Android Developer Verification: Register Your Apps Before They Stop Installing.

What the requirement is

• Who: all developers distributing apps on certified Android devices running Android 7 or higher, whether through Google Play, another participating store or direct download.
• What: verify your identity (individual) or organisation, and register the package names of your apps, which “may include proving ownership of the private signing keys used for those packages”.
• Where: Play Console if you publish on Google Play (and it can also register apps you distribute outside Play); the separate Android Developer Console if you distribute exclusively outside Play.
• Consequence: unverified apps cannot be installed by users on certified devices in the enforcement regions; for Play developers, Google says to register any remaining apps by 30 September 2026 “to avoid global removal from Google Play”.

Timeline (verified 22 September 2026)

If you publish on Google Play

Google’s guidance for Play developers is reassuring on the identity side and specific on the app side:

• “For most Play developers, no new action is required for identity verification. Your existing verified identity … meets this requirement.” Check Settings → Developer account in Play Console.
• New apps created in Play Console are registered automatically. For existing apps, “99% of apps on Play have been registered automatically” — and the remaining 1 % is exactly the set that needs attention. Play Console’s Home page lists apps that still need registration.
• If you use Play App Signing, Google already holds the information to identify ownership and your eligible apps are part of the automatic registration.
• Apps you also distribute outside Play (enterprise builds, direct downloads, other stores) can be registered through Play Console so they remain installable.

If you distribute outside Google Play

• Register in the Android Developer Console: a full-distribution account costs $25 (the same as Play’s registration fee) and requires identity verification; organisations need a D-U-N-S number, which is free but “can take up to 28 days”.
• A limited-distribution account (students, teachers, hobbyists) is free, needs no government ID, and allows sharing with up to 20 specific devices.
• The console lets you add and verify multiple signing keys per package.
• ADB installs are not affected — development and testing continue as before. Users can still install apps from unverified developers through a deliberate “advanced flow” with warnings and a waiting period; that is not a distribution strategy.

The cases that actually cause trouble

You no longer have the signing key

Google is explicit: “If you lose your signing key you won’t be able to register your packages.” Apps on Play App Signing are safe because Google holds the app signing key; apps still signed with a self-managed key that has been lost need a plan — see lost keystore or upload key.

The package name is already in use

If a package name is registered by someone else, your key “may not be eligible to claim it outright”. Google suggests a different package name, or a registration request with additional review — and warns the name may also be used by others. Changing a package name means a new app on Play, with all the migration that implies; the review has to weigh both options honestly.

An agency or freelancer published the app under their own account

The registered developer is whoever owns the account and holds the key. If that is not you, the fix is usually an app transfer to your own verified account plus key handling — see Google Play app transfer. Doing it before the global rollout avoids doing it under pressure.

Personal account, growing business

Organisation verification needs the D-U-N-S number and matching legal details. If the business is not yet registered with Dun & Bradstreet, start that first — the 28-day lead time is real.

Several keys, several channels

Enterprise builds signed with a different key, white-label variants, or a Play build plus a direct-download build each need their keys registered against the package. Inventory them before the console shows you one at a time.

Practical sequence

1. Open Play Console Home and note every app that is not yet registered; open Settings → Developer account and confirm the verification status.
2. List every package you distribute, every channel it ships through, and which key signs each build.
3. For each package: Play App Signing enabled? Key available? Package registered? Conflicts reported?
4. For apps published by a third party: decide between a transfer to your account and a formal agreement in which the publisher registers the app.
5. For non-Play distribution: register in the appropriate console and add every signing key.
6. Fix what the inventory exposes — usually lost keys, agency ownership and missing organisation details — before the global rollout.

Not the same as …

• The closed-testing requirement for new personal accounts (a Play policy about testing, not identity).
• An account termination (an enforcement action; verification does not reinstate terminated accounts).
• Google OAuth app verification (a Google Cloud process for sign-in scopes).

Checklist

• Developer identity or organisation verified in Play Console (or the Android Developer Console)
• Every distributed package registered; Play Console Home shows no pending apps
• Signing keys available and registered for every channel; Play App Signing enrolled where possible
• No unresolved package-name conflicts
• Apps published by agencies transferred or covered by an agreement
• D-U-N-S number in hand for organisation accounts

Frequently asked questions