In the interest of fairness and hopefully for the last time, I ever have to address this, Google has flip-flopped again and promised “sideloading” will not be removed from their version of Android, but instead have to be enabled in the developer settings, using the following “advanced flow”:

To be perfectly clear, this still falls short of what I wanted, but at this point, it is a compromise I’m willing to take, over further pursuing this, through the various available European courts, myself.

Here is their full statement:
https://android-developers.googleblog.com/2026/03/android-developer-verification.html

@thecanine@twtxt.net congrats on the win! Hopefully it will not turn sour with the next “enter period of time here”. It seems flip-flopping is the law of the land around here.

I never got to ask you, are you affected by this as a developer, or end user, or both?

@bender@twtxt.net both, but neither directly. I know every workaround there is, including those used by developers, to test apps, while working on them. However if “sideloading” becomes so tedious, even the more technical users, cannot be bothered to do it, competing appstores and independent developers, not wanting to send their money and ID to Google, loose users at such rate, they likely won’t be able to justify continuing to maintain their projects, people like me rely on.