What Is Android Developer Verification?
Android developer verification is Google's requirement that apps installed on certified Android devices be registered by a developer whose identity has been verified. It creates a verifiable link between a person or organization, a package name and the signing key used for that package.
The rule is not limited to Google Play. It also covers apps distributed through other app stores, and Google plans to extend it to all apps on certified devices, regardless of where they are downloaded. The stated goal is to stop malware authors from hiding behind anonymity and reappearing under new names after removal. Verification checks who you are and which packages you own; it does not review your app's content or functionality.
As of October 2026, enforcement is live only in four countries and only for installs from participating app stores. Google plans a global rollout in 2027 but has not published an exact date.
Timeline
| Date | Milestone |
|---|---|
| 2025 | Requirement announced |
| March 2026 | Verification opens to developers |
| June 2026 | System service that checks registration starts rolling out to devices |
| July 2026 | Developer ID Status API launches globally |
| August 2026 | Android Developer Console API, limited distribution accounts and the advanced install flow launch globally |
| September 30, 2026 | Enforcement begins in Brazil, Indonesia, Singapore and Thailand |
| 2027 | Planned global expansion to all apps on certified devices |
Enforcement applies to certified devices running Android 7 or higher. In the first phase, installs from seven participating stores are checked: Google Play, Samsung Galaxy Store, HONOR App Market, OPPO App Market, Palm Store (Transsion), V-Appstore (vivo) and GetApps (Xiaomi). Sideloading from other sources is not blocked yet.
Who Is Affected
Google Play developers
If you already publish on Google Play, most of the work is done. Play Console developers are registered automatically, and Google says more than 99% of Play apps were registered without any action. Apps that use Play App Signing are claimed automatically. Check your status on the Play Console home page and manually register any app that was not picked up, including apps you also distribute outside Play.
Developers distributing only outside Google Play
If you ship APKs from your website, through alternative stores or to unmanaged devices, you need an Android Developer Console account. A full distribution account costs a one-time $25 fee and requires identity verification.
Students and hobbyists
Limited distribution accounts are meant for students, teachers, hobbyists and personal projects. They need no government ID and no fee, but an app can be shared with at most 20 specific devices. You can upgrade a limited account to a full one later; converting a full account to limited is not supported.
Enterprise apps
Apps delivered through an organization's own store to managed devices are exempt, though Google recommends registering them anyway.
Account Types at a Glance
| Full distribution | Limited distribution | Unregistered app | |
|---|---|---|---|
| Identity verification | Required | Not required | None |
| Fee | $25 one-time | None | None |
| Reach | Any store or channel | Up to 20 devices | Outside verified stores only |
| Install experience | Normal | Invitation from a known developer | Advanced flow or adb |
What Verification Requires
- Identity. Individuals provide a government-issued ID. Organizations need a D-U-N-S number and a website verified through Google Search Console. A D-U-N-S number is free but can take up to 28 days, so request it early.
- Package name registration. You prove ownership of each package name by providing an APK signed with your private key. Multiple signing keys per package are supported.
- Status check. Registration status is shown in Play Console, in the Android Developer Console (Package names tab) and in Android Studio Panda 4 or later.
For CI/CD pipelines or large catalogs, the Android Developer Console API registers and manages package names programmatically, and the Developer ID Status API tells you whether a package name is already registered.
What Happens to Unregistered Apps
In enforced countries, an unregistered app cannot be installed from a participating store. Outside those stores, users can still install unverified apps in two ways:
- adb. Installs over Android Debug Bridge do not require verification, so local development and testing stay the same.
- Advanced flow. A one-time setup for power users: enable developer mode, confirm nobody is coaching them, restart and reauthenticate, wait 24 hours, then confirm with biometrics or PIN. Installs can then be allowed for 7 days or indefinitely, with a warning for each unverified app.
While the advanced flow is turned off, updates to unregistered apps fail unless installed via adb.
Preparation Checklist
- List every package name you ship, on and off Google Play.
- Confirm in Play Console that each Play app shows as registered.
- Back up your signing keys. If you lose a key, you cannot register that package.
- Organizations: request a D-U-N-S number and verify your website in Search Console now.
- Register off-Play apps in Play Console (if you have an account) or in the Android Developer Console.
- If someone else already uses your package name, prefer a new name; keeping it means extra review and the name may remain shared.
- Add a registration check to your release pipeline before the 2027 expansion.
Common Mistakes
- Assuming Play-only means nothing to do. Automatic registration covers most apps, not all of them. Check each one.
- Forgetting flavor builds. White-label or regional builds with their own package names each need registration if they reach users.
- Using a limited account for a public release. The 20-device cap makes it suitable only for testing and personal use.