New post on /r/flutterdev subreddit:
<b>After one year with Flutter this is what I learned</b>
The story began with me waking up a day thinking to have a new personal project. I told myself that are a lot of successful apps out there, someones even with billions of value, so why I can’t make my own and start earning some extra cash?But I had to start with something simple to learn before launch my own “one million project”.​The best way to learn is having a real project you care forLooking for inspiration: crash courseSo I started looking for app ideas and was a surprise to found many apps that do just that: give you ideas. Some of them with a thousands of downloads and hundreds of reviews.However I couldn’t find any with a good user experience, to be more specific, all of this apps had a horrible design and were full of ads. (Seriously even the logos and graphics really sucks).This is how I decided to create <a href="
https://play.google.com/store/apps/details?id=co.getboosted.emprende">my own business ideas app</a> with one focus in mind: to have the best user experience in this app category.I don’t think I hit this goal in the earlier versions. Despite the design and the navigation was better than the other apps, I wasn’t happy at all.Start from the base: A good architectureI wanted and app that not only looks good, but have also a good architecture and free of bugs, so after saw courses, read blogs and watch a bunch of Youtube videos, I opted to try a serverless approach using Firebase/Firestore as the backend.Now I won’t recommend anyone to start with Firebase, you can easily confuse Flutter features with Firebase and get lost between streams and other terms ignoring whats happening behind and how the server/api connection works.Im not saying you not to use Firebase/Firestore, but in my experience you will be more clear and having a good understanding if you start with an API and http requests at the beginning.I have to mention that Firebase offer a set of tools for free without usage limit:Firebase AnalyticsFirebase AuthFirebase Remote configFirebase Cloud MessagesCrashalyticsFirestore also have a features I like: offline content, realtime sync of the data, light speed loading, and all this for free (at least for small projects) without a server maintenance.Things I don’t like: the lack of a CMS, I don’t wanted to have a CRUD in my app so I tried some services like <a href="
https://flamelink.io/">Flamelink</a> and <a href="
https://www.pushtable.com/">Pushtable</a>.Also without having a good architecture you can easily pass the free usage limit. I ended paying Google $25 monthly for 4 months until I decided to move all the content to my own server/API in a shared hosting (LAMP).But thanks to this now I have a better understanding of API usage and Flutter itself.5 TakeawaysStart with a simple project. Avoid those ToDos and Chat apps. You can practice with them to know the power of Dart and Flutter, but the best way to learn is having a real project you care for.Stay away from Firebase/Firestore at the beginning, first try to learn about HTTP request and API connections using <a href="
https://pub.dev/packages/http">http</a> or <a href="
https://pub.dev/packages/dio">dio</a> packages. Once you feel comfortable with this, you can take all the advantages of Firebase.Read all you can about State Management. Once you have a good understanding of the Flutter native State Management, go for the approach you like more: <a href="
https://www.youtube.com/watch?v=oxeYeMHVLII">BLoC</a>, <a href="
https://www.youtube.com/watch?v=MkFjtCov62g">Provider</a>, <a href="
https://www.youtube.com/watch?v=JsjDLHxGz4M">Scoped Model</a> or even Redux. (I personally use Provider).Pick and follow a <a href="
https://medium.com/flutter-community/flutter-design-patterns-0-introduction-5e88cfff6792">Design Pattern</a>. Avoid making your project based on blocks of codes copied from Stack Overflow… like me. (<a href="
https://www.youtube.com/watch?v=DO8…