When you’re working on personal projects, backend-as-a-service is one of the best things the free market has given us. It allows quick backend creation without much of the hassle and (critical) bugs you may encounter.
When we’re developing a Flutter app, Firebase seems like a very logical choice. It comes from Google (that’s where Flutter came in, too), has tons of functionalities, and has a free tier that looks not that bad at first sight. But each time I had to reach out to it, I had that strange “it’s a trap feeling” (you remember Admiral Ackbar, right?).
The article <a href="https://medium.com/easy-flutter/flutter-firestore-authentication-cost-fd482a2d51bf" target="_blank" rel="noopener nofollow">Flutter. Firebase is a trap</a> affirms this feeling. It provides a quite straightforward calculation of what Firebase would cost an indie developer who succeeded in ramping up to 50K-100K (and more) users and how the calculations look.
The good thing is that it also has a few Firebase BaaS alternatives worth considering if you are starting a new project now.

🚀 Calling all Flutter lovers! 
Share code, swap ideas, stay on top of Flutter trends! Whether you're a newbie or a pro, you've found your tribe. Let's build something awesome together! 💙 

Flutter Developers

Using Firebase for personal projects can be appealing due to its functionalities and free tier, but it may lead to unexpectedly high costs for indie developers with growing user bases. Alternatives to Firebase are suggested for those starting new projects.

Article: Avoid Firebase. It's a trap

Firebase is a great to build something fast. We developed a fitness application with around 20k monthly user that still runs on the free tier (auth+firestore).
After 1.5 year of development, the app generate revenue, and we got a quite some room left before starting to pay.
I really think it’s a great tool to start small/indie projects. We save time and money, that we used to ship fast features for users and advertisement.
Because at the end of the day even if you have the most cost effective baas/db but no user to experience it, you are making no money.
This is a feedback from an small application, and I understand that it will not suit large scale application.

Always follow YAGNI and cross the bridge when you get there.
I was bitten by Firebase once and not because of how much it cost but how crappy their feature implementations were.

Thank you for sharing this information.
Our app’s user base is growing steadily every day, and we are utilizing Firebase services for certain parts of the project. We’ll stay mindful of any potential challenges or limitations associated with this.

Will it create a big problem in the future to transfer a medium-large scale project with high monthly active users and using firebase as a backend service to our own backend has anyone ever tried this before? ? (If there is an active working team)

Thanks i was going to use firebase for mi project