Item: Firebase
Rating: 7
Author: Verified User

Overall Satisfaction with Firebase

Use Cases and Deployment Scope

We use Firebase (FB) as a backend for new FlutterFlow projects. It is easily integrated with the product and for a while was the only choice. However I would greatly prefer tabular(SQL) data to FB when it comes to any function that you need to write.

Pros and Cons

Pros

Tight integration with FlutterFlow
Ease of deployment
NoSQL structure allows for easier experimentation

Cons

Functions require learning a different language
There is not a good native UI for viewing/working with data
Google's Constantly changing (deep linking) exhibits noncommittal nature to the product's features.

Return on Investment

Ease of deployment for FlutterFlow projects
Rapid manipulation of database schema
Slight learning curve for those coming from SQL background
40% decline in productivity on projects due to Firebase functions

Usability

Firebase functions are more difficult to use, there are no concepts of triggers or cascading deletes without the use of Firebase functions. Firebase functions can run forever if not written correctly and cause billing nightmares. While this hasn't happened to us specifically it is a thing that happens more than one realizes.

Alternatives Considered

MongoDB, MongoDB Atlas, Supabase, Azure SQL Database and Microsoft SQL Server

Supabase seems to have the best of all worlds right now. Followed by MongoDB/Firebase for smaller projects requiring less manpower and resources. Azure and Microsoft are reserved for existing projects and larger corporate clients.

Key Insights

Do you think Firebase delivers good value for the price?

Yes

Are you happy with Firebase's feature set?

Did Firebase live up to sales and marketing promises?

Did implementation of Firebase go as expected?

Yes

Would you buy Firebase again?

Other Software Used

FlutterFlow, Supabase, Make

Likelihood to Recommend

If you are looking to spin up something quick, a proof of concept, or to be first to market AND your code tool is tightly integrated with Firebase then go for it. Not having to make formal schema changes is definitely helpful. However the error checking involved around that can be a nightmare.

Comments

Please log in to join the conversation

Firebase, still an 8