That's the dark side of these types of dependencies.
But they provide a great deal of utility, so I can understand the attraction.
Just an ignorant and naive outsider's take, but to me it paints a pretty damning picture of the state of mobile development.
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.
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).
The real alternative there would be to use some SQLite syncing solution and a different solution for auth and cloud compute.
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.
pranshuchittora•1h ago
lol768•1h ago
So many problems here, and no signs of an updated SDK that behaves properly on malformed input.