Android developer verification enforcement starts September 30, 2026, two days from today. Google's support page on the program states the scope directly: apps "must be registered by verified developers in order to be installed from selected app stores to certified Android devices" in Brazil, Indonesia, Singapore and Thailand. If your team ships on Google Play, you're almost certainly already covered. If you ship only outside the seven participating app stores listed below, the deadline doesn't reach your app yet, but a related clock already started, and it's worth knowing which one applies to you before Wednesday.
What Android developer verification actually requires
The scope is narrower than the name suggests. Android's developer verification overview names the seven stores in play: Google Play, HONOR App Market, OPPO App Market, Galaxy Store, Palm Store, V-Appstore and GetApps. Protection applies only when someone installs through one of those seven, onto a certified device running Android 7 or newer, in one of the four countries listed above. A device that isn't certified, an OS below version 7, or a country outside the four sits outside enforcement, for now.
HighCircl tracks developer verification alongside Android's other platform changes in Platform and language release notes: what breaks and what to fix.
Does the September 30 deadline apply to your app?
Where your app is distributed changes the answer, and it's worth checking by channel rather than assuming.
If you distribute through Google Play, you likely have nothing to do. A June 2026 update on the verification rollout says "Over 99% of their apps have been registered." Check your Play Console account status anyway. Most teams on Play are fine, but the small share that isn't are exactly who needs to catch this before Wednesday.
Apps distributed through your organization's own store, onto devices your IT admin manages, are exempt. Google's developer verification FAQ puts it plainly: those apps "won't need to complete the verification requirements since your IT admin has vetted them." The same FAQ recommends registering and claiming them anyway, since an employee who later installs the same app from outside the managed store, or onto a personal device, runs into the same install friction as anyone else.
For apps that ship through a store outside the seven, or that users install as a direct APK, September 30 doesn't touch anything. Google's FAQ says these requirements "won't apply to your app yet," and install experiences for your users won't change this month, but it also recommends completing verification before the global rollout in 2027. That's a recommendation today. Next year it stops being optional.
A deadline like this is a good prompt to check whether anyone on the team actually owns Android release admin end to end. For teams weighing whether to hire that ownership in-house, how to hire Android developers covers what that search looks like.
With two days on the clock, the fastest way to triage is: confirm your Play Console verification status if you're on Play, confirm nobody on the team assumed enterprise distribution means "no action needed" (it means "register anyway, eventually"), and if your organization hasn't touched a D-U-N-S number yet, read the next section before you do anything else.
How to register your app before the deadline
1. Decide: full distribution vs. limited distribution account
Google's guide to full distribution accounts covers anyone publishing to the wider public. The limited distribution guide covers a narrower case: sharing apps "with up to 20 devices that end-users have explicitly authorized." Limited distribution is free and carries no ID requirement, and Google says it's "available for everyone," including students and hobbyists distributing to a small group. If your app is headed for a public store, you want full distribution. If it's an internal build going to a handful of named testers, limited distribution is the lighter path.
2. Verify identity: individual ID, or a D-U-N-S number for organizations
Individuals on a full distribution account submit a government-issued photo ID and a proof-of-address document. Organizations submit a D-U-N-S number instead, the nine-digit Dun & Bradstreet identifier used to establish a business's legal identity; if you don't have one, Google says you can get one at no cost from Dun & Bradstreet. The catch is timing: Google's own guidance says the D-U-N-S process "can take up to 28 days." With two days left before enforcement, a team that hasn't already requested one will not have it by September 30. That's a hard limit built into the process itself. If your app is Play-distributed you're most likely already past this step; if it isn't, start the D-U-N-S lookup today regardless of what the deadline requires of you right now, because the 2027 rollout runs on the same 28-day clock.
3. Register your package names in the Developer Console
The Developer Console registration guide lays out three steps. First, enter the package name you want to register. Second, add your key: the SHA-256 certificate fingerprint from your app's signing key pair, which moves the package's status to "In review." Third, for existing package names, prove ownership by signing an APK with your private key and uploading it.
4. Confirm status moves from "In review" to "Registered"
Once Google processes the submission, you're notified by email and the package name's status in the Developer Console updates to "Registered." Don't treat "In review" as done. The registration only counts once the console shows "Registered."
5. CI/CD teams: automate registration via the Developer Console API
The Developer Console API docs describe a public interface built for distributors and individual developers to register package names programmatically instead of one at a time in the console. Most registrations clear without extra steps, but a key registration that needs a justification, a package name or signing keys shared across developers, requires submitting a detailed business rationale for Google to review, and that review can take up to 24 hours. Build that lag into your release calendar if any of your package names or signing keys are shared. If you're already tracking Android 17's per-app memory limits this quarter, add this registration work to the same backlog rather than treating it as a separate fire drill.
What happens on September 30 if you haven't registered
The consequence is narrower than it sounds. Apps from developers who haven't completed registration by the deadline become unavailable for new installation on certified devices, through participating stores, in the four affected countries. That's it. It doesn't remove the app from devices where it's already installed, and it doesn't touch install eligibility anywhere outside those four countries or those seven stores. A user who already has your app keeps it. A new user trying to install it for the first time, on a certified device, in Brazil, Indonesia, Singapore or Thailand, through one of the seven participating stores, hits a wall your competitors who registered in time won't.
Android teams have another hard deadline to track this quarter. Google Play's target API 36 deadline already reset install eligibility once in August.
What still works after the deadline: ADB and the advanced flow
Local development doesn't change. Developers remain free to install apps without verification using ADB, a carve-out built specifically to support developing and testing apps that aren't ready for wider distribution.
For end users, Google is also introducing a one-time advanced flow for people who want to install apps from unverified developers anyway. Per the same June 2026 post's walkthrough of the advanced flow, it starts in developer mode, includes a check that the user isn't being coached through the steps, and requires a restart and re-authentication. Only after a one-day waiting period does the user confirm with biometric or PIN and get the option to enable installs from unverified developers for 7 days or indefinitely. Neither of these is a workaround for a developer who skipped registration. Both exist for users choosing to accept the risk themselves, on their own devices, and neither happens instantly.
What's coming in 2027
Google's own FAQ frames September 30 as an early phase: verification requirements for apps outside Play and outside sideload are set to go global "before the global rollout begins in 2027." The overview page's line on future expansion puts it the same way: "we'll expand this globally to all apps on certified devices." Neither page attaches a specific date, an updated country list, or a specific store list to that expansion. Anything more precise than those two sentences is speculation until Google publishes it.
FAQ
Does Android developer verification apply if I distribute outside Google Play?
Not on September 30. If your app ships through a store outside the seven participating stores, or users sideload it directly, these requirements don't apply yet, and install experiences for your users won't change this month. Google recommends completing verification anyway before the 2027 global rollout.
Do I need to register apps only distributed through my company's enterprise or managed-device store?
Technically no. Apps on an organization's own store, installed to devices the IT admin manages, are exempt because the admin has already vetted them. Google still recommends registering and claiming those apps, since installs from outside the managed store, or onto an unmanaged device, don't get the exemption.
Can I still sideload unverified apps after September 30?
Developers can, always, using ADB, which Google built specifically to support development and testing. End users get a separate, one-time advanced flow instead: it starts in developer mode, checks that the user isn't being coached through the steps, and requires a restart and re-authentication. After a one-day waiting period, the user confirms with biometric or PIN and can then enable installs from unverified developers for 7 days or indefinitely.
What does it cost to become a verified developer?
A full distribution account carries a one-time $25 fee that Google says covers administrative costs. A limited distribution account, capped at up to 20 explicitly authorized devices, is free and doesn't require a government ID at all.
What happens to apps that are already installed if the developer never registers?
Nothing changes for existing installs. The deadline only affects new installations, on certified devices, through the seven participating stores, in the four affected countries. An app already on a user's device stays there whether or not its developer ever registers.