Understanding Android developer verification

To better protect users from repeat offenders, we are adding another layer of security called developer verification. This will help make app installation safer by preventing the spread of malware and scams.

Starting in 2026, Android will require all apps to be registered by verified developers in order to be installed by users on certified Android devices. This creates crucial accountability, making it much harder for malicious actors to quickly distribute another harmful app after we take the first one down. Think of it like an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags; we will be confirming who the developer is, not reviewing the content of their app or where it came from.

This change will start in a few select countries particularly concerned about the impact of these forms of fraudulent app scams, often from repeat perpetrators.

Here's the timeline to help you plan:

November 2025: Early access begins. Invitations will be sent out gradually.
March 2026: Verification opens for all developers.
September 2026: These requirements go into effect in Brazil, Indonesia, Singapore, and Thailand. At this point, any app installed on a certified Android device in these countries must be registered by a verified developer.
2027 and beyond: We will continue to roll out these requirements globally.

Read more in our blog post: A new layer of security for certified Android devices.

Frequently asked questions

General

Is this the end of sideloading on Android?

Sideloading is fundamental to Android, and it's not going anywhere. Our new developer identity requirements are designed to protect users and developers from bad actors, not to limit choice. We want to make sure that if you download an app from a developer, regardless of where you get it, it's actually from them. Verified developers will have the same freedom to distribute their apps directly to users through sideloading or to use any app store they prefer.

If I have an apk and I want to put it on my device and distribute it to my friends/family do I need to go through ID verification?

We recommend you register – it's a simple, one time process that will allow anyone to download your app. However, if you prefer not to, we have a solution for you. We are also introducing a free developer account type that will allow teachers, students, and hobbyists to distribute apps to a limited number of devices without needing to provide a government ID.

If I want to modify an app and install it on my own device, or if I'm a power user, is there a way to turn this verification requirement off?

We understand this is an important use case for many developers and power users. While the verification requirement itself is a core OS feature to help protect the broader ecosystem from malware and can't be turned off, we plan to offer two paths for experienced users to install unverified apps:

Advanced flow: We are building a flow that allows experienced users to proceed with installing an unverified app after going through a series of clear warnings. This new mode is designed to resist social engineering, helping users fully understand the risks, but ultimately gives experienced users the choice to accept the heightened security risk and install the software. We are gathering early feedback on the design of this feature now and will share more details in the coming months.
Android Debug Bridge (ADB): Developers and power users can still use Android Debug Bridge (ADB) to build, test, and install modified or unverified apps on their own devices, which remains the standard method for development work.

What happens if a developer doesn’t verify their identity?

Please be sure to verify your identity and register your apps by the September 2026 deadline. This will ensure your apps remain installable for users. Apps from developers who have not completed these steps by the deadline will be unavailable for new installation on certified Android devices in applicable countries.

Do enterprise apps need to complete the verification requirements?

Apps distributed through your organization’s store, on managed devices, won't need to complete the verification requirements since your IT admin has vetted them for safety and security. However, we recommend app developers still register and claim these apps if they are potentially distributed outside of a managed store or to non-managed devices.

Identity and accounts

What is a D-U-N-S number and how do I get one?

A D-U-N-S number is a unique nine-digit identifier for businesses provided by Dun & Bradstreet. It is required if you are registering as an organization. If your organization does not have one, you can get one for free from the Dun & Bradstreet website. The process can take up to 28 days so you should make preparations to obtain a D-U-N-S number.

How is my personal information handled?

We use your personal information to verify your identity, and it is handled in accordance with Google's Privacy Policy. We are committed to protecting your data. Android developer verification will not change our long-standing, rigorous legal process for responding to government information requests. We will continue to apply the processes that we have today.

Why is there a $25 fee for the Android Developer Console? How can I pay?

The $25 fee for the Full Distribution account in the ADC helps cover administrative costs. We are actively working to support multiple forms of payment to accommodate developers globally and will have more details when the console launches. There is no fee for developers who qualify for a Limited Distribution account.