We use it too, but anything that requires actual funds, we would migrate to AWS or refactor.
Like we'd use to allow PMs to change banners/copy on the fly, but Supabase is better. It does RAG but Supabase does that better too. Firebase functions are really good for prototyping, but once it starts to cost money, we move it to AWS. It's good for feature flagging, and we moved that to Growthbook. Analytics started on Firebase and were moved to open source so we'd own the data. The only thing they do well is Crashlytics and that's free.
If everyone was as bad a customer as us, I would assume they're in trouble.
Unfortunately a lot of people have trust issues with Google. We don't want them controlling data and certainly nothing as core as functions, DB, and feature flagging. Then when people don't use these things, Google kills it real fast.
I suppose, but firebase is used in some applications, though of course a lot of them are just during testing, so assuming everyone was not like you they would make profit, but assuming a mix, they would make only a bit of profit, so it would be more like a small side project/nice feature that google provides that makes them a little bit of money.
Like we'd use to allow PMs to change banners/copy on the fly, but Supabase is better. It does RAG but Supabase does that better too. Firebase functions are really good for prototyping, but once it starts to cost money, we move it to AWS. It's good for feature flagging, and we moved that to Growthbook. Analytics started on Firebase and were moved to open source so we'd own the data. The only thing they do well is Crashlytics and that's free.
If everyone was as bad a customer as us, I would assume they're in trouble.
Unfortunately a lot of people have trust issues with Google. We don't want them controlling data and certainly nothing as core as functions, DB, and feature flagging. Then when people don't use these things, Google kills it real fast.