Android developer verification is rolling out to all developers (Play Console + the new Android Developer Console)
Google is expanding developer verification and app registration ahead of user-facing install protections later this year. Here’s what changes, when, and what to do now if you ship outside Play.
Original post (source): Android Developers Blog - “Android developer verification: Rolling out to all developers on Play Console and Android Developer Console” (March 2026)
What’s happening
Google is rolling out Android developer verification to all developers via:
- Play Console (for Play-distributed apps)
- a new Android Developer Console (for developers who distribute outside Google Play)
The goal is to reduce malware from sideloaded sources, and to make it harder for malicious actors to repeatedly reappear under new identities.
What changes for users (and when)
Google says most users won’t notice any change until later this year.
The key shift is: unregistered apps will require ADB or an “advanced flow” to install, while registered apps keep the normal install experience.
Rollout timeline (as stated in the post):
- April 2026: “Android Developer Verifier” appears in Google System services settings
- August 2026: advanced flow for power users launches globally
- September 30, 2026: requirement begins in Brazil, Indonesia, Singapore, Thailand
- 2027+: expands globally
What changes for developers
If you ship on Google Play
- If you’ve already completed Play Console’s developer verification, Google says you’re likely already set.
- Google also says it will automatically register eligible Play apps for verified developers (with a manual “claim” process in the rare exceptions).
If you distribute outside Google Play (or do both)
- You can create an account in the new Android Developer Console and complete verification.
- Google says you’ll also be able to register apps distributed outside Play in Play Console.
If you’re a student or hobbyist
Google says it’s building a free, limited distribution account (no government ID required) for sharing to up to 20 devices (early access invites in June).
Why this matters (for app growth, not just security)
This is a distribution and trust change that can show up as:
- higher friction for sideload-heavy segments (enterprise distribution, beta communities, niche device ecosystems)
- new “why can’t I install/update this?” support tickets in the affected countries first
- a forced cleanup of “who owns this package name” and signing/ownership hygiene inside orgs
Tiny win: list every way your app is installed today (Play, OEM store, MDM, direct APK, GitHub releases, beta channels). For each channel, confirm who controls signing keys and who will be responsible for verification + registration. That one spreadsheet can prevent a very avoidable September fire.
Read the original: https://android-developers.googleblog.com/2026/03/android-developer-verification-rolling-out-to-all-developers.html
Want help with ASO?
If you want this implemented for your app, check out our services - or run your workflow in APPlyzer.