Prisoners of Google Android Development
3 comments
Been there many years ago, the android ecosystem is as good and intuitive as the languages used to develop apps (poo emoji here).
Make a good web version of your site/app and use a webview, no more endless hours debugging shit.
Yeah this is why the only way to go seems to be PWA, you can publish a PWA to the android app store but if anything goes wrong people can still access it from the web without the app store. With a pure native app when things go haywire we are left with 0 options.
I was not even aware that PWA can be submitted also to the store. But yeah, it's crazy that there does not exist a way to yank/cancel latest release so that no more phones would get the faulty update at least. I was not aware of that possibility before it happened and I hope that this article is a lesson to others too if nothing else.
TLDR; Written an article about a real-life case-study about Android app deployment/development problem where production version has a critical problem and update has been "in review" for 72h+ and there's nothing else we can do.
If there's some (ex)-Googlers who could help to speed up update approval process then I would be really helpful, if not then let it just be as a warning for anyone else being involved with mobile app development.