Bean counters took over, now it's maximum profit extraction until slow decline takes over. Decline in profit mind you, their software and service quality took a dive a while ago.
Apple's web services are shit, so I hope not. When it works it's great/okay, but when it breaks 5-10% of the time (that's about the rate AirDrop doesn't work for me) there's absolutely no indication what the hell is going on. Apple's allergic to progress indicators and useful error messages.
I remember first learning about Firebase when working on Android push notifications, a loooooong time ago (~2011 i think). Over time it grew into this full-featured app development platform, after an aquisition (don’t remember the name).
These days however it feels a bit neglected, and somehow poorly bolted on to GCP. I still have a few production apps running on it and news like this reinforces my belief that it’s in decline.
What are folks using these days that (ideally) is open source and self-hostable? I don’t want to lock in with another platform. Some of these apps use the offline sync feature of Firestore (apps used in basements and other low-connectivity areas).
Using UnifiedPush with ntfy [1] as push distributor, used Prosody as well with Conversations as distributor which did work but I prefer ntfy because it does its one thing well.
Yes that's the sad part, if you want to integrate Push Notification in your app, and you want to use a 3rd party vendor like OneSignal etc, you still need a fuckin FIREBASE account & FIREBASE dependencies in your app. So every app on the Play Store comes with firebase dependency.
Calling them a 3rd party push notification vendor is being generous. Google is still doing the push notification and I guess OneSignal offers a wrapper around the libs.
I guess Supabase is the obvious contender. It doesn't provide the actual frontend hosting though, which is a bit of a pain because now you have two problems.
I wasn't aware that Supabase is self-hostable - thanks for pointing that out, will have a look. Customer is in Europe, if they decide to move away from Firebase, they don't want to migrate to another managed platform run by a US company (digital sovereignty etc.)
Important but also pretty obvious. If literally every iOS app were crashing, I would expect a more generic headline from a major news outlet, not a tweet discussing the cause with ALLLLLL CAPS in the middle of it.
That's true. It's one of those phrases that, for example in an interview, an Indian might not be aware holds them back because of how jarring it sounds to the native speaker. My feeling is that while it's true it's effectively colloquial English in the subcontinent it's also appreciated if people understand rather than everyone being too polite to say anything and never coach the person. While I'm here I will admit I love you the words thrice and the needful
This will be the new normal as all human “engineers” from staff to seniors are now down levelled to interns and junior engineers when using AI; unable to understand what they are doing and pushing broken updates like this into production with “agents”.
So we have not learned anything since then, on both sides from the SDK builder side and the client side.
Why is it that iOS is crashing but not Android?
Google should know better to not have such an incident like this as the Firebase SDK runs on millions of apps.
If you did not implement a fall back mechanism, perhaps you based your testing assumptions on that “Firebase could never crash my app” which is now false.
The coding side of this isn't even the problem - that a broken change like this made it to production is an operational failure.
Why didn't testing catch this? Why was there no canary? How come alarms didn't wake up an on call as soon as the call-volume on the backend dropped? Why was this update rolled out to every customer at once, instead of gradually?
I think verification is still a grey area in the agentic software dev.
QA and ppl testing it often resort to coding agents for the QA work, and we all know how good agents are at convincing themselves.
And in many companies, if they move at a responsible speed (rather than the speed the AI vendors promise, if you let their tools work in yolo mode), that person will get replaced by someone who will just yolo it
Wrong.
They will be totally blamed. And the pushback will be that management forced me to use AI and go fast. Then, management will be the one NOT being blamed for this.
I'm hearing an awful lot of "How could they do this to us?" and not a lot of "Wow, maybe we should have read some of this 3rd party code we bundled into 'ALLLL' of our apps"
Just an ignorant and naive outsider's take, but to me it paints a pretty damning picture of the state of mobile development.
> maybe we should have read some of this 3rd party code we bundled
Not really practical though, if you push the thought to its limit. That 3rd party code is literally everything that's not written by you, from firmware to the launch UI. And if you don't push the thought to the limit then there's always that risk leading to the same "maybe we should've read X" if something happens in X. Trusting that others will be good stewards of all that 3rd party stuff is a hard requirement for making progress.
I appreciate what you're saying. Commercial realities are very different to theoretical ideals, and of course you have to draw the boundary of trust somewhere to get anything done.
I don't think anyone is saying it's an app developers responsibility to ensure the user's bootloader is securely implemented.
There is a lot of space between verify everything and trust nothing, and I don't think it's unreasonable to question whether that trust boundary is in the right place.
I also think that the code compiled to produce the binary you ship is a perfectly reasonable place to put that boundary, would you disagree?
I'm sure that within the mobile dev world it is normal, accepted practice to include lots of unseen code. I don't begrudge anyone involve for taking the money and doing what's expected.
But I still think it's a mad way to run a business or community project, and it's worth considering how we got here and whether it really has to be this way.
I agree its not practical, but including any 3rd party libraries in your project puts it at real risk of upstream bugs. There needs to be acceptance of this rather than blame culture.
Because their client SDK might crash the entire app if the server does something funky. We saw it before with Facebook, and now it's Firebase's turn.
A dependency on code you can't read reaching out to servers you don't control is a recipe for disaster. If you can control the server, you can try to add fixes, redirect DNS to a backup cluster, you name it. If you implement the client, you can write the code in a way that doesn't cause full crashes when the remote server does something weird. If you can do neither, you're handing over your business flow and uptime to a third party that doesn't care about you in the slightest.
The more we insist on the idiotic idea that we can delegate all coding to agents and don't even need to read it anymore, the more such things will happen. And they will accelerate, as the hidden errors will compound.
Well, you don't have to use the proprietary third-party SDKs in your apps... If you want analytics you can either implement your own, or use some open-source ones that aren't dependent on some third party backends switching some features on for everyone all at once...
At least Google engineers can invert a binary tree
What happened to all the leather jacket boys from Google? They were setting the trends in Site Reliability Engineering some 10 years ago.
See this 2016 article for the cultural background: https://cloud.google.com/blog/products/gcp/adventures-in-sre...
Bean counters took over, now it's maximum profit extraction until slow decline takes over. Decline in profit mind you, their software and service quality took a dive a while ago.
Yeah, but better not spend too much time reading AOSP source code.
Don't underestimate them, can also crash linux/plasma https://news.ycombinator.com/item?id=49849626
Lol, but they can't build BREW ;)
Yeah, surely atleast 12 of those engineers tested their SDK thoroughly for a minimum of 14 continuous days[1]. /s
1. https://support.google.com/googleplay/android-developer/answ...
Resolved - https://github.com/firebase/firebase-ios-sdk/issues/16728#is...
Resolved, but can still affect customers for up to 4 hours...
So many problems here, and no signs of an updated SDK that behaves properly on malformed input.
Ugh.
That's the dark side of these types of dependencies.
But they provide a great deal of utility, so I can understand the attraction.
I guess it's time Apple sherlocked Firebase.
Apple's web services are shit, so I hope not. When it works it's great/okay, but when it breaks 5-10% of the time (that's about the rate AirDrop doesn't work for me) there's absolutely no indication what the hell is going on. Apple's allergic to progress indicators and useful error messages.
You can write your own crash reporter now.
I remember first learning about Firebase when working on Android push notifications, a loooooong time ago (~2011 i think). Over time it grew into this full-featured app development platform, after an aquisition (don’t remember the name).
These days however it feels a bit neglected, and somehow poorly bolted on to GCP. I still have a few production apps running on it and news like this reinforces my belief that it’s in decline.
What are folks using these days that (ideally) is open source and self-hostable? I don’t want to lock in with another platform. Some of these apps use the offline sync feature of Firestore (apps used in basements and other low-connectivity areas).
Using UnifiedPush with ntfy [1] as push distributor, used Prosody as well with Conversations as distributor which did work but I prefer ntfy because it does its one thing well.
[1] https://github.com/binwiederhier/ntfy
Yes that's the sad part, if you want to integrate Push Notification in your app, and you want to use a 3rd party vendor like OneSignal etc, you still need a fuckin FIREBASE account & FIREBASE dependencies in your app. So every app on the Play Store comes with firebase dependency.
Calling them a 3rd party push notification vendor is being generous. Google is still doing the push notification and I guess OneSignal offers a wrapper around the libs.
Especially for offline sync Firebase is still much stronger than other all-in-one solutions.
The real alternative there would be to use some SQLite syncing solution and a different solution for auth and cloud compute.
While Firebase has support for queries with realtime updates and offline caching, I wouldn't quite call it offline sync.
I'm working on an alternative (phaselock.io) which is still in alpha but it is open-source and self-hostable.
Offline mode and cross-platform support are some of the features most important to me.
I guess Supabase is the obvious contender. It doesn't provide the actual frontend hosting though, which is a bit of a pain because now you have two problems.
I wasn't aware that Supabase is self-hostable - thanks for pointing that out, will have a look. Customer is in Europe, if they decide to move away from Firebase, they don't want to migrate to another managed platform run by a US company (digital sovereignty etc.)
Yeah, and pinning versions doesn't save you when the config comes from their server.
All iOS apps that are using firebase… It’s an important distinction.
Important but also pretty obvious. If literally every iOS app were crashing, I would expect a more generic headline from a major news outlet, not a tweet discussing the cause with ALLLLLL CAPS in the middle of it.
Exactly the same thing also happened in 2020 with the Facebook SDK:
https://news.ycombinator.com/item?id=23097459
Ironic. They could save others from crashes, but not themselves.
I was wondering why random apps kept crashing today. Good to know.
But this is completely not acceptable from the Google
They’ve been accepting this for years and so have users
This is not the first time this has happened.
A friendly piece of vocabulary assistance: it's "this morning" ("today morning" is not correct English)
It’s a common phrase in Indian English
That's true. It's one of those phrases that, for example in an interview, an Indian might not be aware holds them back because of how jarring it sounds to the native speaker. My feeling is that while it's true it's effectively colloquial English in the subcontinent it's also appreciated if people understand rather than everyone being too polite to say anything and never coach the person. While I'm here I will admit I love you the words thrice and the needful
Keep vibe coding and breaking everything.
This will be the new normal as all human “engineers” from staff to seniors are now down levelled to interns and junior engineers when using AI; unable to understand what they are doing and pushing broken updates like this into production with “agents”.
Better not blame Claude on this outage.
https://news.ycombinator.com/item?id=23097459
So we have not learned anything since then, on both sides from the SDK builder side and the client side.
Why is it that iOS is crashing but not Android?
Google should know better to not have such an incident like this as the Firebase SDK runs on millions of apps.
If you did not implement a fall back mechanism, perhaps you based your testing assumptions on that “Firebase could never crash my app” which is now false.
No matter who writes the code, the name in the commit is responsible as well as the person who approved / reviewed the PR.
The coding side of this isn't even the problem - that a broken change like this made it to production is an operational failure.
Why didn't testing catch this? Why was there no canary? How come alarms didn't wake up an on call as soon as the call-volume on the backend dropped? Why was this update rolled out to every customer at once, instead of gradually?
Why pay for and bother with all of that when you can outsource it to your users?
Users who will forget about it, and due to inertia stay on your platform.
I think verification is still a grey area in the agentic software dev. QA and ppl testing it often resort to coding agents for the QA work, and we all know how good agents are at convincing themselves.
-
The solution is testing it yourself, not more AI
And in many companies, if they move at a responsible speed (rather than the speed the AI vendors promise, if you let their tools work in yolo mode), that person will get replaced by someone who will just yolo it
No matter how many times this is said, the reality is that it is not true: no one will get blamed if the AI can be blamed.
Wrong. They will be totally blamed. And the pushback will be that management forced me to use AI and go fast. Then, management will be the one NOT being blamed for this.
there's a LOT of push from vibecoders to stop with PR reviews.
i've also heard "the prompt is the only thing that should be reviewed"
Just blaming AI seems to be the norm now, we have companies literally hacking other companies by "rogue LLM" and not getting any responsibility for it
I'm hearing an awful lot of "How could they do this to us?" and not a lot of "Wow, maybe we should have read some of this 3rd party code we bundled into 'ALLLL' of our apps"
Just an ignorant and naive outsider's take, but to me it paints a pretty damning picture of the state of mobile development.
> maybe we should have read some of this 3rd party code we bundled
Not really practical though, if you push the thought to its limit. That 3rd party code is literally everything that's not written by you, from firmware to the launch UI. And if you don't push the thought to the limit then there's always that risk leading to the same "maybe we should've read X" if something happens in X. Trusting that others will be good stewards of all that 3rd party stuff is a hard requirement for making progress.
I appreciate what you're saying. Commercial realities are very different to theoretical ideals, and of course you have to draw the boundary of trust somewhere to get anything done.
I don't think anyone is saying it's an app developers responsibility to ensure the user's bootloader is securely implemented.
There is a lot of space between verify everything and trust nothing, and I don't think it's unreasonable to question whether that trust boundary is in the right place.
I also think that the code compiled to produce the binary you ship is a perfectly reasonable place to put that boundary, would you disagree?
I'm sure that within the mobile dev world it is normal, accepted practice to include lots of unseen code. I don't begrudge anyone involve for taking the money and doing what's expected.
But I still think it's a mad way to run a business or community project, and it's worth considering how we got here and whether it really has to be this way.
I agree its not practical, but including any 3rd party libraries in your project puts it at real risk of upstream bugs. There needs to be acceptance of this rather than blame culture.
You're already trusting them with their proprietary cloud products, whose code you can't read. Why wouldn't you trust them with their client SDK code.
Because their client SDK might crash the entire app if the server does something funky. We saw it before with Facebook, and now it's Firebase's turn.
A dependency on code you can't read reaching out to servers you don't control is a recipe for disaster. If you can control the server, you can try to add fixes, redirect DNS to a backup cluster, you name it. If you implement the client, you can write the code in a way that doesn't cause full crashes when the remote server does something weird. If you can do neither, you're handing over your business flow and uptime to a third party that doesn't care about you in the slightest.
Mobile and frontend development, both, now-a-days contain way way way more dependencies than they should.
Yes, but the SaaS adoption is also the reason. Many analytics SDKs, observability tooling etc.
The more we insist on the idiotic idea that we can delegate all coding to agents and don't even need to read it anymore, the more such things will happen. And they will accelerate, as the hidden errors will compound.
If only there was any way to avoid this, right..? (I don't mean from Google's side, that as well, but that's not the point)
No, not under your control. It is like "trust me bro" thing from your dependency maintainers.
Well, you don't have to use the proprietary third-party SDKs in your apps... If you want analytics you can either implement your own, or use some open-source ones that aren't dependent on some third party backends switching some features on for everyone all at once...