30 engineers on Hacker News describe using Firebase first-hand: 6 endorse it, 10 regret it, 3 are mixed.
“Worst auth experience: Firebase on NextJS. Never again.”
regret · personal · throwaway77385 · 2024-10-23 · source ↗ · wrong label?“It has just enough quirks that I now prefer postgres unless I need all of the firebase features desperately.”
regret · personal · quickthrower2 · 2022-10-15 · source ↗ · wrong label?“We ditched all of firebase and I'm happy we made that decision early enough.”
regret · production · swid · 2022-10-15 · source ↗ · wrong label?“I have been using AppScript at my work as well to sync data from a sheet to Firebase and it works quite well.”
endorse · production · anshumankmr · 2021-12-30 · source ↗ · wrong label?“We've switched firebase app to a small postgres instance and have seen all of our performance issues magically melt away.”
regret · production · nicoburns · 2020-10-29 · source ↗ · wrong label?“we built a chat application using Firebase. Within a few months we discovered our customers were receiving their chats out-of-order and it took another few more days to figure out it was due to some Firebase quirks.”
regret · production · kiwicopple · 2020-05-27 · source ↗ · wrong label?“I had to code-review a Django app using Firebase as a DB and swore never again.”
regret · production · aitchnyu · 2019-06-09 · source ↗ · wrong label?“messages suffered outages every now and then... Now we use Firebase only for authentication (via real time database) and Notification sending”
mixed · production · ankit219 · 2018-10-13 · source ↗ · wrong label?“I've been a webdev now for some time, and I've written zero SQL queries. Firebase is nice. So is Mongoose.”
endorse · production · sillysaurus3 · 2017-11-16 · source ↗ · wrong label?“We run entirely on Firebase with Auth, Storage, Hosting, Firestore, and Cloud Functions. As a result, we actually don't have any backend to manage.”
endorse · production · sagadotworld · 2017-10-03 · source ↗ · wrong label?“We would see crazy spikes and we could not get support to fix it. Multi tenancy would occasionally cause other performance issues.”
regret · production · datasage · 2017-04-12 · source ↗ · wrong label?“I don't like it when my critical systems depend on services out of my control, especially when those services go down for hours or days at a time”
regret · production · gamache · 2016-12-06 · source ↗ · wrong label?“Works the treat except for an issue I'm having upgrading firebase tools.”
regret · personal · bungie4 · 2016-12-02 · source ↗ · wrong label?“I might have stuck with Firebase had there been something like that available. Instead, we switched”
regret · production · karmelapple · 2016-01-29 · source ↗ · wrong label?“We run Firebase in production. Offline-first is one of the most important features for us.”
mixed · production · quantisan · 2015-12-14 · source ↗ · wrong label?“I tried Firebase + Angular and liked it well enough, but I found the security rules kind of hard to grasp.”
mixed · personal · rezistik · 2015-07-01 · source ↗ · wrong label?“I've tried Angular and Firebase for a few small protoypes... I really like the User authentication.”
endorse · personal · arrmn · 2015-07-01 · source ↗ · wrong label?“We've been using Firebase now for about 6 months to power Roll20, it's allowed us to grow from 100 to 1,000 concurrents without having to make any changes”
endorse · production · 0.5 yr · silverlight · 2012-12-18 · source ↗ · wrong label?“We've been using Firebase for a while now. The uptime, low-latency, and consistency have been impressive.”
endorse · production · toddmorey · 2012-12-18 · source ↗ · wrong label?“we used firebase and had access to the native authentication SDKs, then we we switched to ory”
neutral · production · edude03 · 2023-04-24 · source ↗ · wrong label?“we were building things with Firebase and other services we didn't control.”
neutral · production · elt · 2022-08-02 · source ↗ · wrong label?“I've done auth0 twice (never again). Firebase once. Cognito at least 4 times.”
neutral · production · jaeming · 2022-07-02 · source ↗ · wrong label?“We use Google Cloud and Firebase at work and our application and servers are still up and running.”
neutral · production · leonidasv · 2020-12-14 · source ↗ · wrong label?“Hasura + firebase auth + serverless functions for any logic”
neutral · production · lukaspili · 2020-02-27 · source ↗ · wrong label?“Hosting costs, well, not too bad. We use firebase.. outgoing data is 10c per Gb”
neutral · production · davidzweig · 2019-12-07 · source ↗ · wrong label?“We use a google app engine/firebase/plotly so we look a bit different to the traditional style”
neutral · production · lee101 · 2017-11-22 · source ↗ · wrong label?“Say for example that you are using Firebase (we use this for a chat app) but do not want to expose keys”
neutral · production · bikamonki · 2015-03-18 · source ↗ · wrong label?“Firebase.com also for persistence but for cases where auto-synch is required.”
neutral · production · bikamonki · 2015-02-10 · source ↗ · wrong label?“The only reason we switched to Firebase was, being a small team, we didnt want to maintain all those servers.”
neutral · production · yeleti · 2014-01-13 · source ↗ · wrong label?“Firebase for more persistent state-sync things like chat and presence.”
neutral · production · RoboTeddy · 2012-11-16 · source ↗ · wrong label?