Android developer verification goes global in January
Google will roll out Android developer verification in all regions starting in January 2027. Apps from unregistered developers will be blocked, including sideloaded apps. Verification needs government ID and a $25 fee, with a free tier for hobbyists.
By JetherVerse News

Google says Android developer verification reaches all regions starting in January 2027, according to Ars Technica on November 19, 2026. The requirement blocks installation of apps from unregistered developers, including apps sideloaded from outside the Play Store.
Verification needs government identification and a $25 fee. Google launched the system in Brazil, Indonesia, Singapore and Thailand in September, and says verification reaches all devices within several months of the global start. Millions of non-Play apps are registered, and Google says these cover more than 99% of global Android app installs. The verifier service already runs on Google-certified devices on Android 8 Oreo or later. Galaxy Store, Honor, Oppo, Xiaomi, Transsion and Vivo stores will list only verified apps once Google flips the switch.
Google changed course after feedback. Hobbyists get a free account to distribute apps to a small group, and the limit rose from 25 installs to 50. A new API streamlines registering application packages. An advanced flow lets users install any app regardless of verification status. The option sits deep in settings, comes with scary warnings and needs a 24-hour wait. The setting is live today.
Google frames verification as a security measure, because identity checks and a fee make malware and scam apps harder to distribute. Ars Technica adds, even with the concessions, the system gives Google a lot more control.
Costs remain. Ars Technica notes developers in sanctioned nations cannot verify their identities, which locks them out of distribution. Sideloading sometimes needs a connection to Google servers, because only popular app IDs are cached on devices. Other installs get checked online first.
For developers, register apps and signing keys before January, including apps shared outside the Play Store. Teams distributing internal or beta builds by APK should confirm the small-group allowance fits their testers. Agencies shipping client apps by direct download should verify early and tell clients about the 24-hour bypass wait.
Read the full report at Ars Technica.
Source: Ars Technica
Get the news in your inbox
The tech stories that matter from JetherVerse News, with the source on every one.

