Android developer verification: live in four countries since September 30, global in 2027, and what to register now

Android developer verification has been enforced since September 30, 2026, but only in Brazil, Indonesia, Singapore and Thailand, and only for installs from seven app stores. Everywhere else, Google plans to enforce it from 2027. If you ship an Android app, inside Google Play or outside it, register now, and choose your account type knowing which details Google publishes.

By the end of this post you will know what changed on September 30, what still installs and what doesn't, what each registration path costs, where Google's own pages contradict each other, and which details about you end up on a public Google Play profile. Everything below was checked against Google's pages in November 2026.

Android developer verification is live in four countries, through seven stores

Google's developer verification guide says the protections went live on September 30, 2026 for users in Brazil, Indonesia, Singapore and Thailand. In this first phase the system checks installs from seven stores:

• Google Play
• HONOR App Market
• OPPO App Market (OPlus)
• Galaxy Store (Samsung)
• Palm Store (Transsion)
• V-Appstore (vivo)
• GetApps (Xiaomi)

The checks run on certified Android devices running Android 7 or higher, and the updates reach phones through Google Play services, according to the developer verification FAQ. For apps distributed outside Google Play, enforcement in this phase covers phones and tablets only. Google still recommends registering every form factor.

The narrow scope matters more than the headline. The same FAQ says that if you distribute through a store outside the list, or users sideload your APK directly, "these new verification requirements won't apply to your app yet." A sideloaded APK on a phone in Jakarta installs as it did before. An unregistered app on Galaxy Store in Jakarta doesn't.

Is Brazil one of the android developer verification countries?

Yes, according to most of Google's own pages. The developer guide, the June 2026 Android Developers Blog post and the limited distribution guide all name Brazil. The Android Developer Console Help article, Understanding Android developer verification, lists only Indonesia, Singapore and Thailand, then refers to "these four countries" in the next sentence. That looks like an editing slip in the Help article, not a policy change. If you have users in Brazil, treat it as enforced.

What happens to unregistered apps after September 30

The Help article says apps from developers who missed the deadline "will be unavailable for new installation on certified Android devices in applicable countries." That applies to installs from the seven participating stores.

Updates are the less obvious problem. The FAQ says unregistered apps can only be installed or updated when the user has turned on the advanced flow or uses ADB (Android Debug Bridge, the command-line install tool). With the advanced flow off, "updates to unregistered apps will fail." So an unregistered app that is already on a phone keeps running, but it may stop receiving your fixes.

Google Play developers have less to do, but they still have a deadline. The June blog post says 99% of apps on Play were registered automatically, and it told developers to register the rest by September 30, 2026 "to avoid global removal from Google Play." If you haven't opened Play Console since the summer, check its Home page for apps that still need registering.

Can I still sideload apps without verification?

Yes. Sideloading still works in two ways. Developers can install any app on their own devices over ADB with no registration and no waiting period. Everyone else can turn on the advanced flow, which the FAQ describes as a one-time setup:

1. Turn on developer mode in system settings.
2. Confirm that no one is coaching you to turn off your security.
3. Restart the phone and sign in again, which cuts off remote access or an active call.
4. Wait one day, then confirm with fingerprint, face unlock or device PIN.
5. Install apps from unverified developers, with the setting on for 7 days or indefinitely. A warning still shows, with an "Install Anyway" button.

For a maker, the advanced flow is a fallback, not a distribution plan. A one-day wait and a developer-mode prompt will lose you most people who just wanted to try your app.

Three ways to register, and what each costs

Which console you use depends on where you ship. If you are on Google Play, use your existing Play Console account, which also handles apps you distribute outside Play. If you ship only outside Play, sign up for the new Android Developer Console. Then verify your identity and register each package name by proving you hold its signing key.

The $25 fee is one-time and, in the FAQ's words, is "similar to Play's $25 registration fee." Google waives it for limited distribution accounts.

Limited distribution account: 20 devices, or 50?

The limit has changed on one Google page and not on the others. The June blog post, the FAQ and the Android Developer Console Help page on choosing a distribution all say 20 devices, and the Help page adds "If you would like to distribute to more than 20 devices, sign up for full distribution." The English limited distribution guide now says users can share apps with "up to 50 devices that end-users have explicitly authorized." Until the pages agree, plan around 20.

Devices are added through a handshake: a QR code or link, consent on the device, and registration in the Android Developer Console. You need a Google Account with 2-Step Verification and a linked Google payments profile, but no government ID. A limited account can be upgraded to full distribution later. A full account can't be turned into a limited one.

Skip limited distribution if your app has any commercial intent. Google's own examples are family apps, portfolio prototypes and classroom projects.

Android developer verification without D-U-N-S

A personal account doesn't need a D-U-N-S number. An organization account does. D-U-N-S is the nine-digit business identifier from Dun & Bradstreet. It is free to get from Dun & Bradstreet, but the FAQ says the process can take up to 28 days, and Google warns that third-party services may try to charge high fees for it. Government entities, and organizations that can't get a D-U-N-S number, can apply to Google support for another way to verify.

Does Google show my home address on Google Play?

It depends on the account type and on whether you make money on Play. Play Console Help's page on required account information sets out what users see:

The address comes from the Google payments profile linked to the account. The same page says that in certain regions developers must provide additional information that may be shown on Google Play, such as a phone number or full address. For a solo maker who sells in-app purchases or paid apps under a personal account, that legal address can be a home address.

The trade-off is direct. A personal account avoids the D-U-N-S wait and stays country-only until you monetize. An organization account takes longer to set up and publishes the organization's legal address and phone, which is only better for your privacy if that address isn't your home. We can't tell you which address to register. That depends on where your company is legally based, and on local company law.

Outside Play it's quieter. Google says the contact email on a limited distribution account won't be shown publicly. The Android Developer Console Help describes the developer name as mainly for telling your own accounts apart.

A checklist before the 2027 global rollout

Google says verification will expand "globally for all apps on certified Android devices in 2027," and that it will soon cover all third-party Android app stores. No exact 2027 date has been published. The steps with long lead times are the ones to start now:

1. Pick the console. Play Console if you are on Play at all, Android Developer Console if you ship only outside it.
2. Decide personal or organization using the address table above, before you start ID checks.
3. Request a D-U-N-S number now if you register as an organization, because of the 28-day lead time. Organizations also have to verify their website through Google Search Console.
4. Find your signing keys. The FAQ is blunt: "If you lose your signing key you won't be able to register your packages." If you use Play App Signing, your eligible apps are claimed automatically. The Developer Console accepts several keys per package.
5. Check your package names. If another developer already uses a name, you may need a different one, or an additional review that may still leave other developers using the same name.
6. Watch the status in Play Console, in the Package names tab of the Android Developer Console, or when you build a signed APK in Android Studio Panda 4 or later.
7. Automate it if you ship many apps. Google's Console API registers package names from a CI pipeline.

Open-source makers who ship through F-Droid have more time, because F-Droid is not one of the seven stores on the September list, so its installs aren't checked yet. That ends with the 2027 rollout, which Google says covers all apps on certified devices.

The strongest case for waiting runs like this. If none of your users are in the four countries and you never ship through those seven stores, nothing has changed for you, and the rules could change again before 2027. Google's own pages already disagree on the limited distribution device limit. But D-U-N-S numbers and lost keys don't get faster under deadline pressure, and an unregistered app's updates will fail on every phone the rule reaches unless its owner has turned on the advanced flow.

Once you're registered, put the app where people can find it. Android itself is listed on Upfynd, and as of November 6, 2026 we list 1,353 products under Developer Tooling and 504 in Open Source. Listing a product is free, and a person on our team checks each one before it goes live. Submit your Android app, then watch where it lands on the launch boards.