Android's developer-verification rollout began on 30 September 2026 in Brazil, Indonesia, Singapore and Thailand. It applies to seven participating stores on certified devices. Direct sideloading is outside this first phase.
Where the first phase applies
- Countries: Brazil, Indonesia, Singapore and Thailand.
- App stores: Google Play, HONOR App Market, OPPO App Market, Galaxy Store, Palm Store, V-Appstore and GetApps.
- Devices: certified Android phones and tablets running Android 7 or later. Google says the checks arrive through Google Play services rather than requiring a new Android version.
Within that scope, participating stores check whether an app is registered to a verified developer before an install or update. Google expects to extend the protections globally in 2027, but its public timeline does not specify a month or a country-by-country order. We have not tested the enforcement on a device, so this is a report of Google's published policy, not a claim that every eligible phone already behaves identically.
What direct sideloading can still do
Google's FAQ says the September deadline applies to the named participating stores. Apps installed directly from a developer's site or from a store outside that list are not covered by this initial phase. The FAQ also says Android Debug Bridge (ADB) installations continue to work. That is the distinction missed by claims that Android has blocked sideloading altogether.
What verification means for a player
A verified developer has linked an app to an identity and registered the package. That does not mean Google has judged the game fair, safe for a child, free of malware or worth buying. It is an accountability check on the distributor, not a review of a game's content. Continue to inspect the publisher, permissions, purchase terms and recent reports as you would for any unfamiliar app.
What to check if an update fails
If you are in one of the four countries and a game from a participating store will not install or update, first check that store's message and the developer's official support channel. An install failure can have many causes; this rule is only one. Avoid downloading an APK from an unverified mirror to work around a store problem. If a game disappears entirely, see what happens when a mobile game shuts down for the separate questions around account access and purchases.
How we worked this out
The geographic scope, participating stores and 2027 timeline come from Google's current Android developer-verification overview and FAQ, checked on 8 October 2026. The 29 September correction to Google's March rollout post clarified that protections would begin rolling out rather than switch on everywhere at once. We did not test an installation, and we make no claim about a particular publisher's registration status.
Sources
- Android developer verification (opens in a new tab) — Google (accessed )
- Frequently asked questions — Android developer verification (opens in a new tab) — Google (accessed )
- Rollout to all developers — 29 September clarification (opens in a new tab) — Google (accessed )
Corrections and updates
Updates
- — Updated the cover with a sourced photograph and recorded its creator and licence.
- — Updated the article after the September rollout and Google's 29 September clarification. Removed pre-deadline advice and narrowed claims to the published scope; no install was tested.
