Google changed the way their are the Gatekeepers. It now is tied to requiring a software developer ID attached to a real person; Developer Verification. [0]
replyAnd how side-loading will have to go through ADB versus just allowing the application to be installed by a file manager.
This is why GrapheneOS and /e/OS have been popping up, along with Linux based alternatives.
Google partially walked that back and now says there will still be a way for end users to enable sideloading for apps without developer verification (unclear what that will look like though):
reply Based on this feedback and our ongoing conversations with the community, we are building a new advanced flow that allows experienced users to accept the risks of installing software that isn't verified. We are designing this flow specifically to resist coercion, ensuring that users aren't tricked into bypassing these safety checks while under pressure from a scammer. It will also include clear warnings to ensure users fully understand the risks involved, but ultimately, it puts the choice in their hands. We are gathering early feedback on the design of this feature now and will share more details in the coming months.
According to keepandroidopen.org they haven't updated their wording yet and no real movement has happened to implement this
reply> Google’s description of the program ↗ continues to state plainly that:
"Starting in September 2026, Android will require all apps to be registered by verified developers in order to be installed on certified Android devices"Now instead of using the excuse that "Apple does it too" they can use the excuse "Apple does it even worse"
reply