Android Developer Verification Is Live: What Game Studios Must Do Now
On September 30, 2026, Google began enforcing Android developer verification. If your studio ships APKs outside Google Play (on Galaxy Store, OPPO, HONOR, your own website or an ad network’s direct-download flow), this is the biggest distribution change since the Play target-API rules.
What actually changed
- Enforcement started September 30, 2026 in four markets: Brazil, Indonesia, Singapore and Thailand. On certified Android devices there, apps from unverified developers no longer install through the normal flow.
- Global rollout follows in 2027. Every certified Android device will apply the same check.
- Verification is tied to the developer identity and the package name, not to the store. A verified developer has to register every package name they distribute.
- Participating stores include Google Play, Galaxy Store, OPPO App Market, HONOR App Market, V-Appstore, Palm Store and GetApps.
Google says more than 99% of Play apps were already registered before the deadline, because most Play Console accounts that had completed identity checks were registered automatically. The risk is concentrated in the apps that aren’t on Play: alternative-store builds, white-label builds, regional variants and old package names nobody remembers owning.
Play Console vs. the new Android Developer Console
These are two separate systems:
| Google Play Console | Android Developer Console | |
|---|---|---|
| Covers | Distribution on Google Play | Distribution anywhere on certified devices |
| Identity check | Existing Play verification | Legal identity (government ID or organization details) |
| Fee | Existing $25 Play fee | One-time $25 registration |
| Package names | Auto-registered for most Play apps | Must be registered for every non-Play package |
If you only publish on Play and your account is verified, confirm your package names show as registered and you’re done. If you publish anywhere else, you need the Android Developer Console as well.
Exceptions that still exist
- Limited-distribution accounts let students and hobbyists share an app with up to 20 devices without ID or fees. They are useful for QA, not for launches.
- ADB installs still work for development.
- An “advanced flow” lets power users install unverified apps after extra confirmation steps and a waiting period. Treat it as an escape hatch, not a distribution channel. Almost no casual player will finish it.
Why this matters for UA and growth
- Alt-store and direct-APK campaigns in the four launch markets break silently. You keep paying for clicks, but installs fail at the device. If you run UA in Brazil or Indonesia through non-Play channels, check install-to-open rates this week.
- Old package names are a liability. Many studios renamed or re-skinned games across regions. Every package you still distribute needs an owner with a verified identity.
- Publisher deals need a clear owner. When a publisher distributes your game, agree in writing whose developer identity the package is registered under. Moving it later is far harder than deciding now.
Checklist for this week
- Export every package name you distribute, including Play, alt stores, web APKs and OEM pre-installs.
- In Play Console, confirm each Play package shows as registered.
- For any non-Play package, create or verify your Android Developer Console account and register it.
- If you’re an organization, make sure the legal entity name matches your business documents, the same way it must for a Play organization account.
- Compare install success in BR, ID, SG and TH before and after September 30. A sudden drop on non-Play channels means a package was missed.
- Plan for the 2027 global rollout now, so you don’t have to fix this under a deadline again.
Need a hand?
We set up and audit Google Play and Android developer accounts for studios, from organization verification and D-U-N-S to package registration and policy compliance. Book a consultation and we’ll check your packages before they cost you installs.
Sources: Help Net Security: enforcement timeline · Testers Community: verification explained