Google’s first Android Developer Verification protections began on Sept. 30, 2026, in Brazil, Indonesia, Singapore and Thailand. The rules apply to participating app stores on certified Android devices running Android 7 or later. The United States is outside this first wave, and Google plans to expand the protections globally in 2027.
The change links a verified developer identity to an app’s package name and signing keys. It does not make Google Play the only distribution channel: developers can use other stores and channels, while users retain ways to install unregistered apps.
What Android Developer Verification registers
Google’s system associates a developer’s verified identity with the package names and signing keys of their Android apps. Developers who use Google Play manage registration in Play Console. Google says eligible Play apps are registered automatically; some off-Play apps, or apps that cannot be registered automatically, may need to be registered manually. Developers distributing exclusively outside Google Play use Android Developer Console.
The first-wave protections cover participating stores including Google Play, HONOR App Market, OPPO App Market, Galaxy Store, Palm Store, V-Appstore and GetApps. An app’s distribution channel and registration status determine which installation route applies on affected devices.
Full Distribution and Limited Distribution
Google offers two Android Developer Console account types for developers distributing outside Google Play. Their main difference is the scale of distribution they are designed to support.
| Account type | Intended distribution | Fee | Distribution limit |
| Full Distribution | Broad distribution | $25 | No device limit stated |
| Limited Distribution | Sharing with a small group | Free | Up to 20 specifically authorized devices |
Limited Distribution does not require government-ID verification. Setup still requires a Google Account, 2-Step Verification and a linked Google payments profile.
Unregistered apps still have installation routes
Android Developer Verification does not make installing unregistered apps impossible. Google documents two routes: ADB installs remain exempt from the verification check, and users can use an advanced flow to install unregistered apps on affected devices. Apps distributed through an organization’s store to managed devices are also exempt.
The advanced flow includes several safeguards: users enable Developer Options, confirm that no one is directing them through the process, restart and reauthenticate, then wait one day before confirming with a PIN or biometric check. They can allow installations for seven days or indefinitely. Developer Options do not have to remain enabled after setup.
Google Play’s closed test is a separate requirement
The 12-testers-for-14-days rule is not part of Android Developer Verification. It applies to qualifying new personal Google Play developer accounts seeking production access: at least 12 testers must remain opted in continuously for the 14 days before the developer applies. Google reviews the application and may request further testing.
That requirement concerns access to production on Google Play. Developer verification instead links identities, app package names and signing keys across distribution channels.
Why some small developers object
The Full Distribution fee can matter to developers making apps that are not expected to earn money. In a post dated Oct. 1, an independent developer objected to paying the $25 fee while returning to Android development. Other individual complaints have focused on account access and the extra work involved in meeting Google Play’s separate testing requirement.
Google says developer verification is intended to make it harder for malicious actors to distribute harmful apps repeatedly. Its first protections began Sept. 30, 2026, in Brazil, Indonesia, Singapore and Thailand; the company plans a global expansion in 2027.
