Google Introduces Android Dev Verification Amid Openness Debate
Google has started rolling out a new Android developer verification system to reduce malicious apps and improve platform security, with the company planning global enforcement in the coming years.
The system, which Google outlined in a blog post, requires developers to verify their identities and register their apps, particularly when they distribute software outside the official Google Play marketplace.
Developers who already distribute apps through Google Play and have completed identity verification may not need to take additional steps because Google will automatically register eligible apps. Developers who distribute apps independently, however, will need to create an account in the Android Developer Console and confirm their identities.
For most users, the app installation experience will remain unchanged. However, users will need to follow an advanced installation process or use Android Debug Bridge (ADB) to install unregistered apps in the future. Google says the change aims to reduce scams that trick users into installing malicious software.
Phased Rollout and Implementation Timeline
Google will introduce the verification requirement gradually, starting in selected markets before expanding the system globally. The company says this approach will give developers enough time to complete verification before the changes affect users.
Key milestones include:
- April 2026: Android Developer Verifier appears in system settings.
- June 2026: Google introduces early access and limited-distribution accounts for students and hobbyists.
- August 2026: Google launches limited-distribution accounts and the advanced sideloading flow globally.
- September 30, 2026: Developers must complete verification in Brazil, Indonesia, Singapore and Thailand.
- 2027 onward: Google expands the system globally.
Developers who use Android Studio will also see their app registration status directly within the development environment when they generate signed app files. This integration will make verification part of existing development workflows.
Balancing Security With Openness
Google says the new system aims to balance Android’s open ecosystem with stronger security protections.
The company reported that its internal analysis found malware more than 90 times as frequently in apps installed from sideloaded sources as in apps downloaded from Google Play.
However, open-source advocates and digital rights groups have criticised the policy. The Keep Android Open movement has coordinated an open letter warning that mandatory central registration could threaten innovation, competition, privacy and user freedom by extending Google’s control beyond its own marketplace to other app distribution channels.
Signatories, including privacy and free-software organisations, argue that the requirement could create barriers for individual developers, small teams and volunteer projects. They also point to potential fees, identity checks and terms that may conflict with the principles of an open ecosystem.
The debate highlights an ongoing tension in the Android ecosystem: Google wants to strengthen security while developers and digital rights groups want to preserve Android’s traditional openness.een enhancing security and preserving the platform’s historical openness.
English 










































































