Android Developer Verification: Dates, Fees, Sideloading

Android developer verification is Google's requirement that anyone who distributes apps to certified Android devices registers their identity and their app's package name and signing key. As of 30 October 2026, it is enforced only in Brazil, Indonesia, Singapore and Thailand, and only for installs from a set of named app stores; a global rollout is planned for 2027 and beyond. Developers can still install their own unregistered builds over ADB, and ordinary users get an opt-in "advanced flow" for installing apps from unverified developers.

The details below come from Google's developer verification page and its FAQ, and are current as of 30 October 2026. Google has revised these pages repeatedly, so check them before acting. Related reading is in our Developers coverage.

What Android developer verification actually is

Verification ties an app to an accountable developer. You register through a console, prove who you are, and then register each package name together with the signing key you use for it. Certified Android devices (those running Google's services, which covers most phones outside a few markets) check that registration when an app is installed or updated.

It is not a code review. Google is not judging whether an app is good or safe in this step; it is checking that a real, identified developer stands behind the package name and key.

Dates: what applies and when

July to August 2026: Google's page lists a global launch of the registration status API in July, and developer APIs, limited distribution accounts and the advanced flow in August.
30 September 2026: enforcement begins in Brazil, Indonesia, Singapore and Thailand on certified devices running Android 7 or later.
2027 and beyond: expansion to all apps on certified devices worldwide, according to Google's timeline.

Which installs are affected in the first phase

Google's FAQ says the September 2026 enforcement is limited to participating stores. The guide lists Google Play, HONOR App Market, OPPO App Market, Galaxy Store, Transsion's Palm Store, vivo's V-Appstore and Xiaomi's GetApps, and says verification will extend to all third-party stores later. Per the FAQ, apps from other stores and sideloaded apps are not covered by the September deadline. Some early coverage described the change as blocking installs "from any source"; the current Google documentation does not say that for this phase.

Two further scope points from the FAQ: in the early regions enforcement applies to mobile and tablet apps, and apps distributed through an organisation's own store on managed devices do not need to complete verification, though registration is recommended.

Who has to register

Anyone whose apps are installed on certified devices from the participating stores in the affected countries and, from 2027, more widely. The route depends on where you distribute:

Only outside Google Play: register in the Android Developer Console.
On and off Google Play: use Google Play Console. Google says Play registers the large majority of apps automatically, and you can add the rest by hand.

The Android Developer Console flow has three steps: sign up, verify your identity, and register package names by supplying the APK signed with your private key. Organisations must also provide a website, verified through Google Search Console. Registering a package name creates a verifiable link between the package name and your signing keys, so keep that key secure.

Fees and account types

Full distribution: a one-time USD 25 fee in the Android Developer Console, matching the Play registration fee. Identity verification is required, and you can distribute through any store or channel.
Limited distribution: free, with no ID verification. It lets you share an app with up to 20 specific devices, for testing and personal use, and installers accept an invitation from a developer they know. Google aims it at students, teachers and hobbyists. An account can move from limited to full, but not back.

D-U-N-S numbers for organisations

If you register as an organisation, you need a D-U-N-S number, the nine-digit business identifier issued by Dun and Bradstreet. Per the FAQ it is free from dnb.com but can take up to 28 days, so start early. Individuals do not need one.

What power users and developers can still do

The advanced flow

For people who want to install apps from unverified developers, Google describes a one-time setup with built-in delay, designed to blunt scams where someone is coached into disabling protections:

Turn on developer mode in system settings.
Confirm that nobody is pressuring you.
Restart the phone and sign in again, which cuts off remote access or an active call.
Wait 24 hours, then confirm with biometrics or your PIN.
Choose to allow unverified installs for 7 days or indefinitely. A warning still appears, and you tap "Install Anyway".

Developer mode does not need to stay on afterwards. If you later switch the flow off, updates to unregistered apps fail.

ADB

Installs over ADB do not require registration and are not subject to the 24-hour wait, so developers can keep testing unregistered builds on their own devices.

Open source and F-Droid

Google has a guide for apps distributed through open-source repositories. Registration is optional; unregistered apps can still be distributed there, but users need the advanced flow to install them. Registered apps keep today's install experience. A developer with a verified console account registers the package name and the SHA-256 fingerprint of the signing key, or of the repository's key if the repository re-signs the app. A repository that integrates with the Console API can do this on developers' behalf.

F-Droid objected to the scheme when it was announced in September 2025. In a public post it argued that central registration, fees and ID requirements would threaten free-software app sources and urged regulators to protect alternative stores. That post predates the limited distribution accounts and the advanced flow, so it is not a statement about the current design. The wider debate over platform control sits within tech regulation and privacy, and more on the software side is under open source.

How to check your status

In Google Play Console or the Android Developer Console, using the account you registered with.
In Android Studio Panda 4 or later, status shows when you generate a signed App Bundle or APK.
Programmatically, through the Android Developer ID Status API that Google documents in its guides.

Frequently asked questions

What is the Android developer verification deadline?

Enforcement began on 30 September 2026 in Brazil, Indonesia, Singapore and Thailand for certified devices on Android 7 or later. Google's timeline puts the global rollout in 2027 and beyond.

How much does Android developer verification cost?

Full distribution costs a one-time USD 25 in the Android Developer Console. Limited distribution, for up to 20 devices, is free and needs no ID.

Can I still sideload APKs on Android?

Yes. Sideloading remains possible through the advanced flow, which includes a 24-hour wait, and developers can still install over ADB without registering. In the first phase, sideloaded apps are also outside the September 2026 enforcement.

Do I need a D-U-N-S number to register?

Only if you register as an organisation. It is a free nine-digit number from Dun and Bradstreet that can take up to 28 days to obtain.

Do apps on Google Play need separate registration?

Google says Play Console registers most apps automatically, and you can register the remaining ones, or apps distributed outside Play, manually there.