BTW, all the GrapheneOS, etc. are still Android phones.
SailfishOS is pretty nice
I might get one next
Obviously this is going to impact the supply of apps, since the market share of custom Android is smaller than even the market share of people willing to sideload or use an alternative store on a mainstream Android phone. Many developers might quit the game.
It wasn't OK in 2003. It wasn't OK in 2014. It isn't OK now. I'm just not sure what anybody can do about it.
[0] https://www.nytimes.com/2003/06/30/business/technology-a-saf...
I hope my tiny datapoint shows up in some aggregated stats somewhere.
It’s use-it-or-lose-it.
The final phase is "AI" monitoring everything you do on your devices. Eventually it won't just be passive, either, but likely active: able to change books you read and audio you listen to on-the-fly without your consent. It will be argued that this ok because the program is "objective".
For anyone else failing to resolve DNS for that domain: https://archive.is/q7w0x
https://grapheneos.social/@GrapheneOS/115090818389369737
> "GrapheneOS doesn't include Google Mobile Services and the requirements for certification aren't relevant to us."
And if what you want is a PDA that runs Linux, there are many options, e.g. https://www.clockworkpi.com/home-uconsole.
https://developer.sony.com/open-source/aosp-on-xperia-open-d...
Basically none of this new restriction will bother me, since I don't run anything but stock AOSP and get all my apps from f-droid repos.
Android is decades ahead of that in security, functionality, utility, devex, and design. It's a fools errand to try and modernize that, over building on top of AOSP.
It does require the developer to make minor adjustments, and most banks are simply too risk averse to agree to doing that (I would know, used to be a senior android app dev at a bank).
[0]: https://grapheneos.social/@GrapheneOS/115062761036828110