Google has announced a revised approach to Android app registration following negative community feedback on its proposed mandatory verification system. The updated framework introduces a two-tier model: a standard verified developer account and a limited free option for personal, educational, and enthusiast use.
Advertisеment
Individuals developing apps for personal use, academic purposes, or hobbyist projects may register for a free account that does not require identity verification. This option permits installation on a limited number of devices but excludes mass distribution. Each target device must be manually authorized by the developer through the Android Developer Console using its unique identifier.
Limited Developer Registration for Android Apps
Starting with the Android 16 QPR2 update in December, the Android platform will integrate a new Developer Verifier service. During installation, the system will access Google’s external servers to confirm that the app’s developer has digitally signed the package and completed verification. Internet access is required for this initial check.
For widely used applications, the system will maintain an on-device cache of verified identifiers to reduce reliance on external validation. Additionally, app catalogs will gain the ability to use pre-authentication tokens, enabling streamlined installations without repeated server checks.
Developer Registration Details
Full verification mandates submission of personal or organizational details. Individual developers must provide their legal name, residential address, email, phone number, and a government-issued ID photo. Organizations must verify a domain and supply a DUNS number. Enthusiast and student accounts bypass ID submission but lack distribution privileges.
After registration, developers must declare their apps’ package names and digital signature keys. To prevent impersonation, they must prove control over the signing key used for existing applications.
ℹ️ Google will restrict verified accounts found distributing malicious software or enabling its spread through compromised credentials. All apps linked to such accounts will be blocked from installation across user devices.
Google acknowledges scenarios where developers require anonymity. The company states it will not publicly disclose registrants’ personal data, though it reserves the right to comply with lawful requests from authorities.
Google will keep ADB sideloading
Direct app installation via the Android Debug Bridge (adb) remains unaffected. Users can enable developer mode and connect their device to a computer. Development, testing, and debugging through Android Studio will also continue without disruption, as it relies on adb as well. Enterprise deployments managed through centralized tools also remain exempt from the new requirements.
Impact on third-party stores
The new system will not go well with catalogs like F-Droid, which compiles and signs apps independently of original developers. Google’s policy prohibits third-party registration of apps under another developer’s identity, citing risks of identifier hijacking and naming conflicts. So the newly revealed option doesn't solve concerns raised by F-Droid earlier.
Package name collisions will be resolved by preserving the name of the application with the highest installation count. Less popular apps must adopt new package identifiers.
The rollout
App verification components will arrive in Android 16 QPR2 this December. Older Android versions will receive the change through a Google Play Protect update. Full availability for all developers begins in March 2026. Mandatory enforcement starts in September 2026 in Brazil, Indonesia, Singapore, and Thailand, with a global phase-in planned for 2027.
Support us
Winaero greatly relies on your support. You can help the site keep bringing you interesting and useful content and software by using these options:
