In short: Android developer verification means that apps must be registered by a developer whose identity Google has verified before they can be installed on certified Android devices. It has been enforced in Brazil, Indonesia, Singapore and Thailand since 30 September 2026, for installs from seven participating app stores, and Google says it will expand globally to all apps on certified devices in 2027. If your company ships an Android app, especially as an APK from your own website or through a third-party store, verify your identity and register your package names and signing keys now.
Key takeaways
- Since 30 September 2026, Google requires apps installed from participating stores in Brazil, Indonesia, Singapore and Thailand to be registered by verified developers, on certified devices running Android 7 or later.
- Google states it will expand verification globally "for all apps on certified Android devices in 2027"; as of 3 November 2026 no month has been announced.
- Google Play registered about 99% of Play apps automatically; developers who distribute only outside Play use the new Android Developer Console, which charges USD 25 for a full distribution account.
- Organisations need a D-U-N-S number, which Google warns can take up to 28 days, and a website verified in Google Search Console.
- Installs through ADB are not affected, and power users can install unregistered apps after a one-time "advanced flow" with a 24-hour wait.
What is Android developer verification?
Android developer verification is Google's programme that links every Android app to a real, verified person or organisation. It has two parts: identity verification, where the developer proves who they are with official documents, and package name registration, where the developer proves they own an app by providing an APK signed with the app's private signing key. Google says verification concerns the developer's identity only and does not collect information about app content or functionality.
This guide is by the ApexlyTech team at Apexly Technologies (Pvt) Ltd, which builds and publishes Android and cross-platform apps for businesses, including apps distributed outside Google Play.
What is the Android developer verification timeline?
| Date | Milestone |
| March 2026 | Verification opened to all developers in Play Console and the Android Developer Console |
| June to July 2026 | System service rolled out to devices; Android Developer ID Status API launched globally |
| August 2026 | Android Developer Console API, limited distribution accounts and the advanced flow launched globally |
| 30 September 2026 | Enforcement for installs from participating stores in Brazil, Indonesia, Singapore and Thailand |
| 2027 | Global expansion to all apps on certified Android devices (month not yet announced) |
The seven participating stores in the first phase are Google Play, Samsung Galaxy Store, HONOR App Market, OPPO App Market, Xiaomi GetApps, vivo V-Appstore and Transsion's Palm Store. Google says the capability "will soon be expanded to all third-party Android app stores". Pakistan, Saudi Arabia and the UAE are not in the first phase, but the 2027 expansion is described as global.
Who needs to register, and where?
Every developer who wants their app installable on certified Android devices without extra steps needs to register. The right console depends on how you distribute.
| If you distribute | Use | Notes |
| Only on Google Play | Play Console | Most Play apps were registered automatically; apps using Play App Signing are claimed automatically |
| On Google Play and elsewhere | Play Console | Register off-Play apps and their keys in the same account |
| Only outside Google Play | Android Developer Console | USD 25 for a full distribution account |
| To up to 20 devices (students, hobbyists) | Limited distribution account | No government ID and no fee |
Google's June 2026 blog post told Play developers to register any remaining apps by 30 September 2026 "to avoid global removal from Google Play", so check Play Console if any app shows as unregistered. Apps distributed through an organisation's managed store to managed devices do not need verification, though Google recommends registering them anyway.
What happens to unregistered apps?
Where enforcement applies, unregistered apps cannot be installed or updated from participating stores on certified devices. They can still be installed with ADB, or by users who have turned on the advanced flow. Google's FAQ also notes that if a user turns the advanced flow off again, updates to unregistered apps will fail.
How does the advanced flow work?
The advanced flow is a one-time setting that lets a user install apps from unverified developers. The user enables developer options, confirms nobody is coaching them, restarts and re-authenticates, then waits 24 hours before confirming with a biometric or PIN. After that they can allow unverified installs for seven days or indefinitely, and still see a warning on each install. For a business app, this is not a distribution strategy: most customers will not do it.
What should app owners do now? A step-by-step plan
- List every Android app you ship, including internal tools, POS and driver apps, kiosk builds and white-label variants, with package names and where each is distributed.
- Find your signing keys. Google warns that if you lose a signing key you cannot register the package. Confirm who holds each keystore and move keys into a secure key management setup.
- Get a D-U-N-S number if you register as an organisation. Dun & Bradstreet provides it free, but it can take up to 28 days.
- Verify your organisation's website in Google Search Console; organisations must provide one.
- Choose the console. Use Play Console if you have one; otherwise create an Android Developer Console account.
- Register package names. Upload an APK signed with each key. If a package name is already in use by someone else, you may need an additional review or a new package name.
- Automate it. Google's Android Developer Console API registers package names and manages keys from CI; the Status API checks registration status. Android Studio (Panda 4 and later) shows the status when you build a signed APK or bundle.
- Brief whoever builds your app. If an agency or freelancer published it under their own account or key, sort out ownership now, before 2027.
Technical notes for sideloaded and white-label apps
Businesses in Pakistan and the Gulf often distribute APKs directly: delivery-rider apps, field sales apps, POS terminals and apps for customers' own staff. Each of these will need a verified developer and a registered package name once enforcement reaches those countries. White-label products that ship one codebase under many package names need each package registered, and the Console API is the practical way to do that at scale. Keep build pipelines reproducible and keystores out of developer laptops; a supply chain compromise that steals a signing key is now also an identity problem, which our npm supply chain attack guide covers from the build side.
How ApexlyTech can help
We build and maintain Android and cross-platform apps for businesses and can inventory your apps and keys, set up organisation verification and package registration, automate registration in your CI, and move signing keys into a managed setup. See our mobile app development service or contact us.
Frequently asked questions
Is Google blocking sideloading on Android?
No, but it is adding identity checks. Apps from verified developers install as before from any source. Unregistered apps can still be installed with ADB or after the user enables a one-time advanced flow with a 24-hour wait. Enforcement started on 30 September 2026 in four countries and expands globally in 2027.
Does Android developer verification apply in Pakistan yet?
Not yet. As of 3 November 2026, enforcement covers installs from participating stores in Brazil, Indonesia, Singapore and Thailand. Google says verification will expand globally to all apps on certified Android devices in 2027 but has not given a month, so Pakistani developers should register before then.
How much does Android developer verification cost?
A full distribution account in the Android Developer Console costs a one-off USD 25, similar to Google Play's registration fee. Developers already on Play Console use their existing account. A limited distribution account, for sharing an app with up to 20 devices, has no fee and needs no government ID.
What do I need to register an organisation for Android developer verification?
An organisation needs a D-U-N-S number from Dun and Bradstreet, which is free but can take up to 28 days, a website verified in Google Search Console, identity documents for the organisation, and, for each app, an APK signed with its private signing key to prove ownership of the package name.
Do enterprise apps on managed devices need verification?
No. Google's FAQ says apps distributed through an organisation's own store to managed devices do not need to meet the verification requirements, because the IT administrator has vetted them. Google still recommends registering them, so installs keep working if the app reaches a non-managed device or another source.
Sources
All sources checked 3 November 2026.