Google’s New Android Developer Verification: What You Need to Do

Beginning September 2026, all apps installed on certified Android devices (whether via the Play Store, third-party app stores, or sideloading) must be tied to a verified developer identity. Learn what’s changing and whether you need to adjust to it.

Mandatory Developer Verification Across All Install Methods

Apps must be distributed by developers who have completed identity verification. This applies even to apps installed outside Google Play, effectively reducing anonymity in sideloaded content.

New Android Developer Console for Sideloading Developers

If you distribute apps outside the Play Store, you'll need to use a new Android Developer Console (separate from Play Console) to complete verification and register package names. A lighter-weight version of this console will be available for students and hobbyists.

Timeline & Rollout Strategy

• October 2025: Early access begins. Developers can sign up here to register interest in the early access program: https://google.qualtrics.com/jfe/form/SV_0UnoFWJKl77kwV8

  
  

• March 2026: Developer verification opens for all developers.
  
  

• September 2026: Enforcement starts in Brazil, Indonesia, Singapore, and Thailand. Certified devices in these regions will only accept apps from verified developers.
  
  

• 2027 and beyond: Global rollout expands these requirements worldwide.

The Two Pillars of Verification: Identity and Ownership

The foundation of the new policy rests on two distinct but interconnected requirements that every developer distributing apps for certified Android devices must fulfill.   

Identity Verification

This step is designed to establish a verifiable, real-world identity for every developer account. The specific information required is tiered based on account type. For individuals creating a "Personal account," the process involves providing and verifying their legal name, legal address, email address, and phone number. In some cases, this might be corroborated by uploading an official government-issued ID. 

For entities registering as an "Organization account," the requirements are more stringent. They must provide not only their legal name and address but also a D-U-N-S number. The D-U-N-S number, issued by Dun & Bradstreet, is a global standard for identifying businesses. The process to obtain one can take 30 days or more, introducing a significant administrative lead time for unincorporated or newly formed organizations. This requirement serves as a de facto business filter, raising the barrier to entry for loosely organized development groups and ensuring that any entity operating as an "organization" has a formal, traceable business registration.   

Package Name Registration

Once a developer's identity is verified, they must then prove ownership of their applications and formally register them. This involves linking the app's unique package name (e.g., com.example.app) and its cryptographic app signing key to their verified identity. This process creates a formal, verifiable chain of ownership. When a user attempts to install an app, Android will be able to check that the app's package name and signing certificate are registered to a developer who has passed the identity verification process.

This mechanism is crucial for preventing impersonation, where a malicious actor distributes a fraudulent app using the name and branding of a legitimate one. It also makes it substantially more difficult for a developer who has been banned for policy violations to simply create a new, anonymous account and republish the same or a similar harmful app.   

Simplified Registration for Existing Play Developers

If you already publish via Google Play, the Play Console will support all necessary steps,  including identity verification and package name registration for apps distributed both on and off Play. In most cases, Google will automatically register package names for your Play apps. Manual steps are only required in rare cases (e.g., apps with unknown signing keys or policy suspensions).

How to Complete Android Developer Verification

Google has outlined two primary verification flows: one for existing developers (mostly on Play Console) and one for new developers, including those distributing apps outside of Google Play.

If you're distributing apps through third-party app stores, direct downloads, or enterprise channels, you’ll need to register via the new Android Developer Console.

Learn more

Read the official Google guide. Also, sign up for My App Monitor newsletter to stay up to date with any new Google policy changes.