Android Developer Verification: What Google Play Developers Need to Know

Android developer verification is Google's program that links apps to verified individuals and organizations. Android requires apps on certified devices to be registered by verified developers. Google says protections started on September 30, 2026 in Brazil, Indonesia, Singapore and Thailand, with a global rollout in 2027. For most Play developers, no new identity action is required.

Android developer verification is one of the biggest changes to Android app distribution in years, and it is easy to confuse with the identity checks Play Console already runs. This guide sets out only what Google states on its own pages: Android developer verification, the verification guide, Register on Google Play Console and the verification FAQ. Where Google doesn't say something, we say so instead of guessing.

What is Android developer verification?

Google describes Android developer verification as a program that links real-world entities, meaning individuals and organizations, with their Android applications. Android requires all apps to be registered by verified developers for users to install them on certified Android devices.

Google's stated reason is safety. It says identity verification establishes accountability, creating a connection between apps and their creators that makes it much harder for malicious actors to quickly distribute another harmful app after the first one is taken down. Google also says the program deters bad actors who prefer to operate anonymously.

What is the timeline?

These are the milestones Google publishes. We list only the dates Google states.

WhenWhat Google says happens
August 2026Developer APIs, limited distribution accounts and the power-user advanced flow launch.
September 30, 2026Protections begin for all users who install apps from participating stores in Brazil, Indonesia, Singapore and Thailand on certified devices running Android 7 or higher.
2027 and beyondVerification is expanded globally for all apps on certified Android devices.

For the four starting countries, Google lists the participating stores as Google Play, HONOR App Market, OPPO App Market, Galaxy Store, Palm Store, V-Appstore and GetApps. Google says that if you use a store not on that list, the requirements won't be enforced for your apps during this initial phase, but you should still prepare ahead of the global rollout in 2027.

Who does it apply to?

Google says the requirements apply to all certified Android devices running Android 7 or higher, with updates delivered through Google Play services. Some cases are treated differently:

  • Apps on Google Play: if you distribute on Google Play, your apps across all form factors must be registered.
  • ADB installs: apps installed using ADB won't require verification, so developers can build and test apps that aren't ready for wider distribution.
  • Enterprise apps: apps distributed through an organization store on managed devices won't need to complete the requirements, although Google recommends registering them anyway.
  • Sanctioned countries: Google says the checks won't run on certified devices physically located in comprehensively sanctioned countries.

What do developers need to do?

Google lists three steps:

  1. Have the right console account. Sign up for an Android Developer Console account if you distribute apps outside Google Play. Google says you are registered automatically if you distribute your app through Google Play.
  2. Verify your identity. Provide information and documentation to confirm your identity as an individual or an organization.
  3. Register your package names. Prove ownership of your apps by providing the APK signed with your private key, to connect it with your developer account.

Organizations need a D-U-N-S number. Google's FAQ says you can get one free from Dun & Bradstreet, and that the process can take up to 28 days.

What changes if you publish on Google Play?

Google's page for Play developers says you must use Play Console to manage your Play package names, and you can also use it to register apps you distribute outside Google Play. For identity, it says that for most Play developers no new action is required: your existing verified identity, such as for Play's developer verification requirements, meets the requirement. You can confirm your account information under Developer Account on the Settings page in Play Console.

For package names, Google says 99% of apps on Play have been registered automatically using information you have already provided, but you should check your Play Console Home page. If you use Play App Signing, Google says your eligible apps are part of the automatic registration. You can see each app's registration status on the Android developer verification page in Play Console.

What does it mean for your closed test?

Google's verification pages don't describe testing tracks separately, so here is only what they do say that touches a new app in testing. For new apps, Google says that when you create an app in Play Console, Google Play automatically registers the package name and links it to your account. If another developer already uses that name, Play Console prompts you to choose a different one.

The closed testing requirement is a separate rule, published in Google's App testing requirements for new personal developer accounts. Personal accounts created after November 13, 2023 still need a closed test with at least 12 testers opted in continuously for at least 14 days before they can apply for production access. Our guides to 12 testers for 14 days and closed testing requirements cover that rule.

Is it the same as Play Console identity verification?

Not quite. Play Console has its own account checks, described in Get started with Play Console: when you set up a developer account you verify your developer identity information, and new personal accounts must verify that they have access to an Android device using the Play Console mobile app before they can make their app available on Google Play. Google's verification page for Play developers says this existing verified identity meets the Android developer verification requirement for most Play developers.

What are the distribution options?

Google describes three paths:

PathBest for (Google)Identity verificationDistribution
Full distributionOrganizations and professional developers with wide distributionYesAny app store or channel you choose
Limited distributionStudents, hobbyists and other personal useNoUp to 20 devices
Sideloading unregistered appsDevelopers who are not verifiedNoChannels outside app stores that require verification

Google says a full distribution account in the Android Developer Console has a US$25 fee, which it waives for developers who qualify for limited distribution. Power users can install apps from unverified developers through a one-time advanced flow that includes a one-day waiting period.

What happens if you don't verify?

Google's FAQ says that if you don't verify your identity and register your apps by September 30, 2026, your apps cannot be installed from participating stores in select regions on certified Android devices. Google also notes that if you lose your signing key, you won't be able to register your packages, and it strongly recommends a secure key management solution.

Frequently asked questions

Do Google Play developers need to do anything for Android developer verification?

For most Play developers, Google says no new action is required for identity verification, because the existing verified Play identity meets the requirement. Google registered 99% of apps on Play automatically, but says you should check your Play Console Home page.

Which countries does the September 30, 2026 start apply to?

Google says the protections that began on September 30, 2026 apply to users who install apps from participating stores in Brazil, Indonesia, Singapore and Thailand on certified devices running Android 7 or higher.

Does Android developer verification change the closed testing rule?

No. Google publishes the closed testing requirement separately: personal accounts created after November 13, 2023 still need at least 12 testers opted in continuously for at least 14 days before production access.

Do apps installed with ADB need verification?

No. Google says apps installed using ADB will not require verification, so developers can build and test apps that are not yet ready for wider distribution.