Google's Android developer verification requirement reached its first enforcement date on September 30, 2026. From that date, according to Google's developer verification guide, apps must be registered by a verified developer to be installed or updated on certified Android devices in Brazil, Indonesia, Singapore and Thailand. The United States and United Kingdom are not in this first phase, but Google says the requirement will expand globally in 2027, so every business with an Android app has preparation to do.
Quick answer
If your app is only on Google Play and your Play Console account has already passed identity verification, Google has most likely registered the app for you, and you only need to confirm that in Play Console. If you distribute an Android app outside Google Play (a download from your website, a partner app store, or devices you ship to customers), you need a verified developer account and a registered package name. Without them, the app cannot be installed or updated by ordinary users in the four launch countries now, and the same will apply elsewhere once Google expands the rule.
What was announced
Google confirmed the schedule in an Android Developers Blog post dated June 18, 2026, written by Matthew Forsythe, Director of Product Management for Android App Safety. The post states that app registration becomes required on September 30, 2026 for participating stores in Brazil, Indonesia, Singapore and Thailand. An earlier post dated March 30, 2026 opened verification to all developers through two consoles: Play Console for Google Play developers and the new Android Developer Console for those who distribute elsewhere.
The verification guide describes three steps: sign up for a console account, verify your identity with official documentation, and register each app's package name by proving you hold the private key that signs it.
Status of each part, as described in those sources:
- Released and available now: identity verification and app registration in Play Console and the Android Developer Console; limited distribution accounts; the advanced installation flow for apps from unverified developers (both scheduled by Google for August 2026).
- In effect from September 30, 2026: the registration requirement for the seven participating stores in the four launch countries.
- Announced, no exact date: expansion to all third-party Android app stores, and global enforcement, which Google places in 2027.
Key details
| Item | What Google's documentation says |
|---|---|
| First enforcement date | September 30, 2026 (guide) |
| Countries in the first phase | Brazil, Indonesia, Singapore, Thailand |
| Devices covered | Certified Android devices running Android 7 or higher (FAQ) |
| Participating stores at launch | Google Play, HONOR App Market, OPPO App Market, Samsung Galaxy Store, Transsion Palm Store, vivo V-Appstore, Xiaomi GetApps |
| Google Play apps | Google says 99% were registered automatically. The Play Console policy deadlines page lists September 30, 2026 as the date by which remaining Play apps must be registered to avoid removal from Google Play. |
| Apps distributed outside Google Play | Require an Android Developer Console account. The FAQ lists a USD 25 fee for a full distribution account. |
| Organizations | Need a D-U-N-S number, which the FAQ says can take up to 28 days to obtain, and must verify their website through Google Search Console. |
| Limited distribution accounts | For students and hobbyists: up to 20 devices, no government ID and no fee. |
| Managed company devices | The FAQ says apps delivered through an organization's store on managed devices do not need verification, though Google still recommends registering them. |
| Global expansion | 2027, with no specific date published. |
What happens to an unregistered app
Google's FAQ states that unregistered apps can only be installed or updated through ADB, a developer tool, or after the user enables the advanced flow. That flow is deliberately slow: the user turns on developer mode, confirms they are not being coached, restarts the phone, and waits through a one-time, one-day period before confirming with a fingerprint, face unlock or PIN. Most customers will not complete that process to install a business app. If the advanced flow is off, updates to an unregistered app fail.
What this means for your business
The following is our practical interpretation, not a statement from Google.
Play-only apps are low risk but not zero risk. Automatic registration covered almost all Play apps, so the task is a check, not a project. The exceptions matter because the stated consequence is removal from Google Play.
Apps outside Google Play carry the real work. Typical examples are an APK offered on a company website, apps preloaded on point-of-sale terminals, kiosks or delivery handhelds, and apps published only in a device maker's store. A US or UK company that sells such a product to customers in Singapore or Brazil is affected today, even though its home market is not.
Account and key ownership become business questions. Registration ties a package name to a verified legal identity and to a signing key. If an agency or a former contractor created your developer account or holds your signing key, sort that out now. The FAQ is direct that a developer who loses the signing key cannot register the package. It also notes that when a package name is already in use, a claim may need additional review.
Lead time is the main cost driver. The fee is small. The effort is in gathering company documents, obtaining a D-U-N-S number if you lack one, proving website ownership and locating keys for older apps. None of this depends on which framework built the app; a Flutter or React Native app has an Android package name and signing key like any native one. Our comparison of native, Flutter and React Native development covers the separate SDK and target API requirements.
What to do now
- List every Android app your company distributes, including internal tools and apps installed on hardware you sell, and note each distribution channel.
- Open the Play Console Home page and confirm each Play app shows as registered.
- Confirm the developer account belongs to your company's legal entity, not to an individual employee or a vendor.
- Find out where each app's signing key is stored, who can access it, and whether it is backed up securely.
- If you distribute outside Google Play, create an Android Developer Console account, complete identity verification and register your package names.
- If you register as an organization and have no D-U-N-S number, apply for one early.
- If you have users in Brazil, Indonesia, Singapore or Thailand, test installation and update on a certified device in those markets.
FAQ
Does Android developer verification apply in the US and UK yet?
Not as of October 4, 2026. Google's guide limits the first phase to Brazil, Indonesia, Singapore and Thailand and says the protections will expand globally in 2027. Google has not published a date for the US, the UK or any other country, so treat 2027 as a planning window and prepare the same way in both markets.
Our app is only on Google Play. Do we need to do anything?
Usually only a check. Google's March 30, 2026 post says developers who completed Play Console verification are already verified and that eligible Play apps are registered automatically. Review the Play Console Home page for any app that still needs to be registered manually.
Are internal apps on company-managed devices affected?
Google's FAQ says apps distributed through an organization's store on managed devices do not need to complete verification, because an IT administrator has vetted them. Google recommends registering them anyway so that installation works if the app is ever installed from another source or on an unmanaged device.
Conclusion
Under Google's published schedule, Android developer verification became a condition of distribution in four countries on September 30, 2026, and is due to become one everywhere in 2027. For most Play-only apps the job is a short confirmation; for apps distributed outside Google Play it is an administrative task with real lead time, centered on identity documents, account ownership and signing keys. If you are unsure who controls your Android developer account or keys, or you need help registering or maintaining an app, our Android app development team can review your setup; contact us to start that conversation.
