If you haven’t seen this yet, Google is planning to require mandatory developer
identity verification for all Android apps, including apps distributed outside
the Play Store, taking effect September 2026. This affects every independent
and open source Android developer directly.
This is not just about the Play Store. After September 2026, on any certified
Android device, applications from unverified developers will be blocked by
default. The only proposed bypass, the “advanced flow”, exists only as a
blog post and has not appeared in any beta, dev preview, or canary release.
No one outside Google has seen it.
Google made some noises in a blog post, but beyond that there is no evidence that they have changed direction. I guess you can take them at their word if you want, but that seems rather naive given the context.
This entire flow is delivered through Google Play Services, not the Android OS, meaning Google can modify, restrict, or remove it at any time without an OS update and without any user consent. The advanced flow has still not appeared in any Android beta, dev preview, or canary release. As of the date of this update, it exists only as a blog post and UI mockups. The community is being asked to accept a product announcement as a functional safeguard five months before the mandate takes effect.
Until Google provides a shipping implementation that can be independently verified, our position remains unchanged: all apps from non-registered developers will be blocked once their lockdown goes into effect in September 2026.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: [email protected]
DROID DOES
Welcome to the Android community on Lemmy. Here you can participate in amazing discussions and events relating to all things Android.
5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.
6. Memes are not allowed to be posts, but are allowed in the comments.
7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.
8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.
Google made some noises in a blog post, but beyond that there is no evidence that they have changed direction. I guess you can take them at their word if you want, but that seems rather naive given the context.
They came out with more information on what their walk back looks like. More information is on the website https://keepandroidopen.org/