Android developer verification is designed to link real-world entities (individuals and organizations) with their Android applications. Android will require all apps to be registered by verified developers in order to be installed by users on certified Android devices. This guide explains what you need to do.
Why these changes are happening
Android's developer verification protects users by deterring bad actors and making it harder for them to repeatedly spread harm.
How this helps you
A safer, more trusted ecosystem benefits the entire developer community.
- Deters bad actors who prefer to operate anonymously.
- Makes it harder to spread harm by linking bad apps to their developers. This helps us hold developers accountable, enforce safety policies, and remove malicious networks.
- Boosts user confidence, helping you build relationships with new users and establish trust.
What you need to do
Complete these steps:
Sign up for an Android Developer Console account if you distribute apps outside of Google Play. You will automatically be registered if you distribute your app through Google Play.
Verify your identity: Provide information and documentation to confirm your identity as an individual or an organization.
Register your package names: Prove ownership of your apps by providing the APK signed with your private key to connect the APK with your developer account.
| Choose how to distribute your apps | |||
|---|---|---|---|
| Full distribution | Limited distribution | Sideloading unregistered apps | |
| Best for | Organizations and professional developers with wide distribution. | Students, hobbyists, and other personal use. | Developers who are not verified. |
| Identity verification required? | Yes | No | No |
| Distribution | Distribute from any app store or channels you choose (your company website, etc.) | Distribute to up to 20 devices | Distribute from any channels you choose (outside of app stores that require verification). |
| Your users’ experience | Nothing changes from today’s experience | Accept invitation to install from a developer you know | Use advanced flow to sideload unregistered apps with extra safeguards that gives critical time and space needed to break the cycle of potential coercion. |
|
|||
Timelines and milestones
We’re taking time to incorporate your feedback and give you time to prepare. Here's what to focus on at each stage:
Date |
Milestone |
Developer focus |
|---|---|---|
August 2025 |
New Android developer verification requirements announced |
Learn about the new requirements and sign up for early access. |
November 2025 |
Early access began |
If invited, start your identity verification and app registration. |
March 2026 |
Registration opens for all developers |
Begin your identity verification and app registration for all apps you want to remain installable on certified Android devices. Sign up for early access to limited distribution accounts. |
June 2026 |
Early access starts for limited distribution accounts |
If invited, create your account and share your feedback. |
August 2026 |
Limited distribution account launches globally Advanced flow for users launches globally |
If limited distribution accounts are for you, create your account and register your apps. |
September 2026 |
Regional enforcement begins |
Verify compliance to avoid installation blocks on your apps in Brazil, Indonesia, Singapore, and Thailand. |
2027 and beyond |
Global enforcement |
The rollout continues worldwide. |
Key concepts
Before you start, review these key terms:
- Android Developer Console (ADC): A console for developers who distribute apps only outside of Google Play.
- App signing key: The certificate used to sign your APK.
- Certified Android devices: Google enforces Android developer verification requirements on these devices. If your app runs on a certified device, these requirements apply to you, regardless of your app's download source.
- Google Play Console (PDC): The console for developers who distribute apps on Google Play. If you have a Play Console account, use it to complete the verification requirements.
- Identity verification: The process of providing information and official documentation to verify your identity as an individual or organization.
- Package name registration: The process of creating a formal, verifiable link between your app's unique package name and signing keys.
- Search Console: Organizations need to provide their organization's website. This will need to be verified using Google Search Console.
Find your path
Use the following table to find the correct console and instructions for your situation.
If you distribute apps... |
Next Steps |
Only on Google Play |
Use your existing Play Console account. |
Both on and off Google Play |
Use your existing Play
Console account. Play uses the information you've already shared to automatically register your apps. |
Only outside of Google Play |
Create an account in the Android Developer Console. |