Google is preparing a global launch of Android developer verification. The protections have been live since 30 September 2026 in Brazil, Indonesia, Singapore and Thailand, and the global rollout begins in January 2027. Here is what changes and what your team should do now.
All facts come from the Android Developers Blog post.
What is happening
Verification was announced in 2025 as an extra security layer that makes it harder for bad actors to repeatedly spread harm. After more than a year of preparation with partners, protections went live for participating stores in four countries. The global rollout starts in January 2027 with seven distributors: Google Play, Galaxy Store, Honor, Oppo, Xiaomi, Transsion and Vivo. Over several months the protections will expand to all countries and all installation sources on certified Android devices.
Registration so far
According to Google, millions of apps have been registered since verification opened to everyone in March. They represent over 99% of all Android app installs globally, via any distribution channel.
What was added based on developer feedback
- Limited distribution accounts for students and hobbyists: share apps without registration fees or a government ID check. The authorized-device limit grew from 20 to 50.
- Android Developer ID Status API and Android Developer Console API: automate app registration from CI pipelines for teams with many apps.
- An advanced flow for power users: install an unregistered app by knowingly accepting the risk, while guardrails against social-engineering scams stay in place for everyday users.
A checklist for your team
- You publish on Google Play: check package registration status in Play Console and register any unregistered apps, including those you distribute outside Play.
- You distribute only outside Google Play: create an Android Developer Console account, verify your identity and register your apps.
- You publish on open-source registries: Google has a dedicated guide for registering existing and new apps.
- You manage many apps: consider registering through the API from CI instead of by hand.
Google says registering an app takes under ten minutes. The risk of skipping it is that installing your app stops being seamless wherever the protections are live.
Bottom line
There is little time before January, and the work is simple: inventory packages, verify the account, register the apps. Teams that hand out builds outside Google Play (enterprise, regional and test channels) should be especially careful.



