Folks, if you build apps for Android, there is a new requirement coming whether you like it or not. Google has begun rolling out Android developer verification across both the Android Developer Console and the Play Console, effectively forcing developers to verify their identity and register their apps before they can be widely installed on certified Android devices.
Google says the goal is safety. According to the company, its analysis shows there is more than 90 times as much malware coming from apps installed outside of Google Play compared with apps distributed through the official store. That statistic is being used to justify the new verification system, which Google claims will make it harder for malicious developers to hide behind anonymous accounts.
Still, let’s be honest here. While Google frames this as a security upgrade, it also represents yet another layer of control over the Android ecosystem. Developers who want their apps to install normally will now have to verify their identity and register their apps with Google’s system. In other words, the company is tightening its grip a bit, even on software that is not distributed through its own store.
For many developers already publishing through Google Play, the change may not require much extra work. Anyone who has completed the Play Console’s developer verification requirements will likely already be covered, and Google says it will automatically register eligible apps where possible. If the system cannot automatically register an app, developers will have to go through a manual claim process.
Developers distributing apps outside the Play Store are also affected. They will need to create accounts in the new Android Developer Console and register their apps there. Over time, unregistered apps will trigger additional warnings or require more complicated installation steps.
The rollout will not hit users everywhere immediately. Google plans to begin enforcing the requirement first in Brazil, Indonesia, Singapore, and Thailand starting September 30, 2026. From there, enforcement is expected to expand globally sometime in 2027.
To keep Android looking open, Google is still allowing sideloading. Power users will be able to install unregistered apps using ADB or a new advanced installation flow. That means the door is technically still open, but Google is clearly adding more friction to the process.
There is also a new component coming to Android devices called Android Developer Verifier. Beginning in April 2026, users will start seeing it inside Google System Services settings. The service will check whether apps are registered to verified developers before allowing installation on certified devices.
Google is also trying to avoid alienating hobbyists. Students and small developers will be able to create free limited distribution accounts that allow apps to be shared with up to 20 devices without needing government identification. Early access for that program is expected to begin in June.
Whether this move truly improves security or simply pushes Android closer to a more controlled ecosystem is something the community will likely debate for a while. Android has always prided itself on being open. With requirements like this rolling out, some developers may wonder how open it will feel in the years ahead.
2 thoughts on “Google clamps down on Android developers with mandatory verification”