Hello FlutterFlow Community,
In recent months, we've witnessed and enjoyed the incredible growth not only within the FlutterFlow team and community but in the development of FlutterFlow itself. This evolution has sparked vital discussions about establishing a set of best practices that can guide us all.
Why Best Practices?
Best practices are essential as they help us create more efficient, reliable, and maintainable applications. They ensure that everyone, from beginners to seasoned developers, can benefit from collective wisdom and proven strategies.
A Call for Community Input
I would love to create a dedicated platform where we can discuss these best practices. To kick things off, I'd like to discuss potential categories for these practices. Different roles within our community bring unique perspectives and expertise. For instance, Pooja Bhaumik on the livestream a few weeks ago had mentioned in passing the best practice for naming variables and where the location of logic should be with components and Andrew Daniels has given us countless concepts when it comes to design best practices from all his livestreams (best of luck on your future endeavors!!).
Here's is a preliminary list of categories to consider:
UI/UX Design
Application Architecture (folder structure)
State Management - what should be in app/page/component state
Backend Integration - Firebase/Supabase/API/custom
Security - Auth and Access rules for your db
Testing
Custom Code
This list is just a starting point. I encourage everyone to contribute ideas, suggest new categories, and share your thoughts on how we can make this platform beneficial for all.
Your Feedback Matters
What do you think of this initiative? What categories should we include? Your input is crucial as it will shape this platform to be as inclusive and helpful as possible.
Looking forward to your thoughts and contributions!
All the best,
Joseph Karman