Android developer verification is live: an OEM store compliance checklist

Direct answer — what does Android developer verification enforcement mean for games distributed on OEM stores? Since September 30, 2026, Google’s Android developer verification applies to installs from seven named stores — Google Play, HONOR App Market, OPPO App Market, Samsung Galaxy Store, Transsion Palm Store, vivo V-Appstore and Xiaomi GetApps — for users in Brazil, Indonesia, Singapore and Thailand, on certified Android devices running Android 7 or higher. If your developer identity is not verified and your package name is not registered, Google says your app cannot be installed from those stores in those countries. Outside those four countries, and outside those seven stores, nothing changes yet — but Google says it will expand the requirement globally in 2027.

This checklist is for studios and publishers who ship on Play plus one or more OEM stores: whether you are compliant, what breaks if you are not, and what to lock down before 2027 turns a four-country requirement into a worldwide one.

What exactly started on September 30, 2026?

Google’s developer verification page states that on September 30, 2026, “Protections begin for all users who install apps from participating stores in Brazil, Indonesia, Singapore, and Thailand on certified devices running Android 7+.” The guides page lists the participating stores as Google (Google Play), Honor (HONOR App Market), OPlus (OPPO App Market), Samsung (Galaxy Store), Transsion (Palm Store), vivo (V-Appstore) and Xiaomi (GetApps). As of October 1, Google’s developer pages still carry that date and that country list; we found no official announcement of a delay.

The mechanics matter. In June 2026 Google said it was “rolling out a new system service that will be automatically installed on most Android devices”, which “will be used later this year to verify developer registration.” Enforcement is the device refusing the install, not primarily a store delisting your game. Google’s Help Center phrases the consequence as apps being “unavailable for new installation on certified Android devices in applicable countries.”

One inconsistency to be aware of: that same Help Center page for the Android Developer Console lists only Indonesia, Singapore and Thailand. The developer.android.com guides and Google’s June 2026 announcement both list Brazil as well. Plan on the four-country reading — a compliance plan built on the shorter list is the one that fails.

Three scope limits are just as important as the rule itself:

• Only the seven participating stores. Google’s FAQ is explicit: “The September 30, 2026 deadline only applies to the specific participating stores. If you distribute your app through other stores, or if users sideload your app directly, these new verification requirements won’t apply to your app yet.”
• Only certified devices on Android 7 or higher. The FAQ says the requirement “will apply to all certified Android devices running Android 7 or higher.”
• Unverified apps are not banned from the platform. Google’s June post says “Unregistered apps can be sideloaded with Android Debug Bridge (adb) or advanced flow.” Google’s March 2026 post describes the advanced flow as a one-time power-user setup with “a one-time, one-day wait” before the user can confirm. For a commercial title, that is not a distribution path.

Which OEM store channels does this actually touch?

For a games publisher, the list is the story: every major OEM store a studio would add to a Play listing to reach Indonesian, Thai or Brazilian players is on it. If OEM stores were your “easy” route in these markets, that route now runs through the same identity check as Play.

Smaller independent stores, aggregator storefronts and direct APKs are, per Google’s FAQ, not covered “yet” — a temporary gap, not a strategy. Google’s June announcement says “we will expand these protections globally for all apps on certified Android devices in 2027.”

Which OEM stores to prioritise commercially is covered in our head-to-head on Galaxy Store, GetApps and AppGallery; this article covers the compliance layer underneath. Mapping a specific title against these channels and running the store-by-store operations is what our distribution offer is for.

Am I already compliant? It depends on how you ship

Google’s guides describe three paths, split by distribution footprint.

Your setup	Where you verify	What Google says
Google Play only	Play Console	Package names created in Play Console are registered automatically. “For most Play developers, no new action is required for identity verification.”
Google Play plus OEM stores	Play Console	Play Console can be “the single place to manage all their verification requirements, including for their apps distributed outside of Play.”
OEM stores only, no Play listing	Android Developer Console	”If you distribute apps only outside of Google Play, use the Android Developer Console to manage your developer identity and register your app’s package names.”

Play-first studios are mostly covered — but check, don’t assume. Google’s Play Console guide says “99% of apps on Play have been registered automatically” and asks developers to check their Play Console Home page. Apps using Play App Signing are part of automatic registration. The residual risk is in edge cases: titles not on Play, legacy package names, and OEM builds signed differently from your Play build.

OEM-only publishers have real work. If you ship a title exclusively through Galaxy Store, GetApps or another OEM channel you need a full distribution account on the Android Developer Console. Google’s FAQ states that “The $25 fee for the Full Distribution account in the ADC helps cover administrative costs”, comparable to Play’s own $25 registration fee.

Prototype and test builds have a free lane. The limited distribution account lets you “share apps with up to 20 specific devices for testing and personal use at no cost and without ID verification.” Useful for playtests on OEM hardware, not for a launch.

The post-deadline compliance checklist

Run this per title and per store. The typical failure is one build, on one store, signed with a key nobody registered.

1. Confirm your developer identity is verified on the right console. Play developers: Play Console. Off-Play-only publishers: Android Developer Console, full distribution account. Organisations need a D-U-N-S number — Google describes it as “a unique 9-digit identifier for your organization provided by Dun & Bradstreet” — plus a website verified through Google Search Console and official organisation documents. Individuals submit a government-issued photo ID and proof of address. Google says the process “typically takes about 10 minutes if you have all of the required information ready” — the real time sink is the documents.
2. Inventory every package name you ship, on every store. Include regional variants, OEM-specific builds and legacy titles no longer on Play. Anything not on Play is not covered by Play’s automatic registration.
3. Inventory every signing key behind those packages. A studio that uses Play App Signing on Play but self-signs the APK it uploads to GetApps or Palm Store is shipping the same package name under two keys. Google’s FAQ says the Android Developer Console “lets you add and verify multiple signing keys for a single package” — so register each key you actually sign with.
4. Register the missing packages. In the Android Developer Console you enter the package name, add the SHA-256 certificate fingerprint of your signing key, and, for an existing package name, prove ownership by uploading an APK signed with your private key. Play developers do the equivalent from Play Console.
5. Check status, don’t infer it. Google lists three places to see registration status: the Android developer verification page in Play Console, the Package names tab in the Android Developer Console, and Android Studio when you generate a signed App Bundle or APK (Android Studio Panda 4 and higher).
6. Secure your keys. Google’s FAQ is blunt: “If you lose your signing key you won’t be able to register your packages.”
7. Watch for package-name conflicts. Where a package name is already in use, Google may tell you your key is “not eligible to claim it outright” and suggests a different package name; requesting the name anyway triggers an additional review.

What we don’t know yet — and what to ask your OEM partners

Google documents the device-side check, not the store side. The pages we reviewed do not say:

• whether participating OEM stores will hide or delist unverified apps in the four countries, or simply let the install fail on the device;
• how updates to copies already installed before September 30 are treated — the Help Center wording covers “new installation”;
• how Google’s check interacts with each store’s own developer onboarding. Transsion’s Palm Store, for instance, already requires real-name developer verification of its own; nothing in Google’s documentation suggests one replaces the other.

If you have live titles on these stores in Southeast Asia or Brazil and the wider LATAM market, ask your partner manager at each OEM store, in writing, how unverified listings are being handled in-store from September 30, and whether they report failed installs. If you distribute through Palm Store mainly for Africa, note that no African country is in the first wave — until 2027.

What to watch before the 2027 global rollout

Google has not published a 2027 date on the pages we reviewed. Two practical consequences:

• Your compliance perimeter widens from seven stores to all distribution. Today, smaller stores and direct APKs are out of scope. In 2027 Google says the requirement covers all apps on certified devices. Register off-store builds — web-shop APKs, partner-hosted builds, aggregator storefronts — now, while a mistake costs four countries, not all of them.
• Plan for tooling, not a one-off clean-up. Google’s June 2026 roadmap scheduled the Android Developer ID Status API, which checks whether a package name is registered, for July 2026, and the Android Developer Console API, which registers and manages package names from your development environment, for a global launch in August 2026. If you ship many builds across many stores, wire the status check into release.

FAQ

Does Android developer verification apply to apps distributed outside Google Play?

Yes, but in stages. Since September 30, 2026 it applies to installs from seven participating stores — Google Play, HONOR App Market, OPPO App Market, Samsung Galaxy Store, Transsion Palm Store, vivo V-Appstore and Xiaomi GetApps — for users in Brazil, Indonesia, Singapore and Thailand. Google’s FAQ says that for other stores or direct sideloading, the requirements “won’t apply to your app yet”. Google says it will expand verification globally for all apps on certified Android devices in 2027.

What happens to an unverified app on an OEM store in the four first-wave countries?

Google says apps from developers who did not verify and register “will be unavailable for new installation on certified Android devices in applicable countries” when installed from participating stores. Users can still install unregistered apps through adb or Android’s advanced flow, a one-time power-user setup with a one-day wait. Google’s pages do not say whether OEM stores will also delist those apps, so confirm with each store.

Do I need the Android Developer Console if I already publish on Google Play?

Usually not. Google says most Play developers need no new identity verification and that Play Console can manage verification for apps distributed outside Play too. The Android Developer Console is for developers who distribute only outside Google Play; its full distribution account costs $25. Students and hobbyists can use a free limited distribution account that covers up to 20 devices.

Is there a deadline after September 30, 2026?

Google has announced global expansion in 2027 but has not published a specific 2027 date on its developer verification pages. The four-country phase is already in force, so finish registering OEM-only titles, legacy packages and alternative signing keys now.

---

Developer verification turns OEM distribution into one identity and one package registry every channel depends on. Getting it right across Play, Galaxy Store, GetApps, Palm Store and the rest — before 2027 makes it global — is the kind of channel operations work our Founding Developer Program takes off a studio’s plate.