Google Android developer verification rollout

Google has initiated the first phase of its Android Developer Verification system, a security measure designed to curb malware and fraud by verifying developer identities. The rollout began on September 30, 2026, in Brazil, Indonesia, Singapore, and Thailand.

The system operates at the system level on devices running Google Mobile Services, affecting certified devices running Android 7 or newer. It checks if an app’s package name and signing key are registered with a verified developer in Google’s console; if an app is unregistered or uses an altered key, the default package manager will block the installation.

While sideloading remains possible, Google has introduced significant friction for installing APK files from unverified developers. Users attempting to bypass these restrictions must navigate an advanced process involving enabling Developer Options, authenticating, restarting the device, and waiting a mandatory 24 hours before completing the installation via biometric or PIN authentication. Google states this friction is intended to combat social engineering and fraud by “breaking the sense of urgency used by scammers to guide victims through malicious installations.” ADB installations are currently exempt from this waiting period.

The initiative has faced criticism from various groups. In Russia, officials expressed concern that the requirement for developers to prove their identity could block local applications and create obstacles for programmers and users seeking independent software. Additionally, power users and open-source advocates have argued that the changes complicate third-party app stores and modding ecosystems. Google plans to expand this verification system globally across certified Android devices in 2027.