Starting 30 September 2026, on certified Android devices running Android 7 or later in Indonesia, Brazil, Singapore and Thailand, apps from participating stores need a registered, verified developer behind them before they'll install or update. That's straight from Android's own developer documentation.
What This Means in Practice
It's an identity layer, confirmation of who published an app, with nothing to do with whether the app itself carries a valid digital signature. Android is stacking this on top of what already exists, not swapping anything out. Mostbet is one of the apps this catalog tracks in the Indonesian market, though whether any specific developer distributes through a participating store is something to check directly rather than assume.
What Changes in Indonesia
Android 7 or later, certified devices, apps from the first wave of participating stores - that's the scope. A global rollout across every install source, sideloading included, is slated for 2027. So 30 September 2026 is the early, store-scoped version of this, not the finished product.
First Wave of Stores
- Google Play
- HONOR App Market
- OPPO App Market
- Galaxy Store
- Palm Store
- V-Appstore
- GetApps
Two Different Things
Android has always been explicit about this: every APK needs a digital signature before it installs or updates. That's app signing, and it verifies a specific build's integrity. Developer verification is new, and it confirms who published the app in the first place. Signed but unverified is a real, different category from unsigned, which Android has simply never allowed.
Three Ways to Distribute Under the New Rules
Android splits this into three tracks, and they don't all carry the same requirements. Full distribution - through an app store or a developer's own site at scale - needs real identity verification, including a Google Search Console-confirmed website for organizations. Limited distribution skips identity verification entirely but caps a developer at 20 registered devices, which is aimed squarely at students and hobbyists building for their own use. Sideloading - installing outside any app store, which is how a catalog like this one works - doesn't require identity verification either, but it does route through the advanced-settings warning flow described below.
Installing From an Unverified Developer
There's a one-time, advanced-settings flow for knowingly accepting that risk - a disclosed choice, not a loophole someone found. Android's own guides frame it as giving users "the critical time and space needed to break the cycle of potential coercion," aimed at scam patterns where someone is talked into installing something in the moment. As 2027's global rollout gets closer, expect to see it more often, not less. ADB and local development workflows aren't touched by any of this - that stays exactly as it is today.
How the Rollout Actually Gets There
| When | What Happens |
|---|---|
| June 2026 | System service and limited-distribution early access begin rolling out |
| July 2026 | Status API launches globally; Console API and limited distribution reach early access |
| August 2026 | Console API, limited distribution and the advanced sideloading flow go available globally |
| 30 September 2026 | Regional enforcement begins in Brazil, Indonesia, Singapore and Thailand |
| 2027 and beyond | Global rollout to all certified Android devices, across every install source |
Play Protect Keeps Working
Nothing here replaces it. Play Protect already blocks internet-sideloaded apps that declare specific sensitive permissions - READ_SMS, RECEIVE_SMS, the notification-listener permission and the accessibility-service permission are the ones Google names, since they're the permissions most often abused for financial fraud. Developer verification runs alongside that rule, not instead of it.
What It Means for This Catalog
1xBet is another app tracked on this catalog across those four countries - the same rule would apply to it too, for whichever of its distribution channels touch a participating store.
Indonesia is one of four markets we track for Android platform share, and Android market share across Asia gives the wider picture of how big that install base actually is.
