Thank you for this article.
Alexio Vay

Yep. Lots has changed since I wrote the original article. The pricing has come down and the Firebase platform has gained some maturity. In fact, when the original article was written Firebase didn’t even have much ability to store files. In general, I think the pricing is a bit high still for Firebase. I’ve built a few apps on the platform and I always end up needing to integrate some other server resources (AWS, Digital Ocean, etc.). The built-in resources are somewhat crude in my opinion and it’s a choice between working around the weirdness of the built-in features or picking up some other non-firebase services. In the end, the hosting bill usually slots above other stacks (somewhere around the $50/month mark when all is said and done). However, you don’t need to worry much about scaling at that cost.

After a few projects in, however, I did notice that Firebase tends to move features in and out rather ungracefully. The transition from Firebase 2 to 3 was awful — the environment had a nag screen to update, but didn’t disclose that you’d need to re-write portions of your app if you did the upgrade. I clicked the button 5 days before a site launch and it caused a cascade of re-writes.

Show your support

Clapping shows how much you appreciated Kyle’s story.