Re:Prisoners of Google Android Development
by kobalsky on Sunday August 27, 2023 @07:02PM
(#37287489)
but bugs slip testing all the time, that why even “the pros” have to use staged deployment trick, which takes us to the root problem: releasing on android is like running through a minefield.
there are a million “shoulds”. just because you know most of them or can afford to account for them on every release doesn’t excuse google for the maintenance nightmare that the android ecosystem is.
Re:Prisoners of Google Android Development
by scarface_74 on Sunday August 27, 2023 @07:15PM
(#37287595)
I mean yes there are a million “shoulds”. But logging into your app to see if login works is kind of basic. It was the definition of amateur hour.
Re:Prisoners of Google Android Development
by Ozzie_osman on Sunday August 27, 2023 @07:19PM
(#37287612)
> And having a phase roll out with a rollback is also not a new concept.
Having a quick revert is also "not a new concept". Most modern devops practices focus not just on Mean Time to Failure, but Mean Time to Recovery, and a quick revert is a critical part of that. Even Google's own SRE best practices encourage that.
This is a poor excuse. Even if it were a web app, you would still need to test on multiple browsers.
Doing a smoke test on a new release is just basic professionalism.
And having a phase roll out with a rollback is also not a new concept.