Google's Android developer verification enforcement begins September 30

Google's developer verification enforcement for Android starts on September 30, 2026, in Brazil, Indonesia, Singapore and Thailand. Installing or updating an app on a certified device there will require the developer to be registered with Google, whatever the download source. Google's guidance calls this a checkpoint on the install path, not a ban on sideloading.

What changes on September 30

The rules cover installs from Google Play and the participating stores: HONOR App Market, OPPO App Market, Galaxy Store, Palm Store, V-Appstore and GetApps, run by Samsung, Transsion, vivo and Xiaomi. Developers who already verified in Play Console get eligible apps registered automatically, so most users will see no change.

Apps from unregistered developers keep two paths. ADB installs keep their "workflow and experience the same," Google says, and a power-user advanced flow lets people install unverified apps after a one-time setup. Outside the four countries nothing changes on September 30; the global rollout is planned for 2027.

Inside the advanced flow

Google's published steps are designed to break coercion scams. A user enables developer mode, confirms that nobody is coaching them, restarts the phone and reauthenticates, then returns after a one-time, one-day wait to confirm with biometrics or the device PIN. Google says the pause breaks the urgency scammers rely on; it does not apply to ADB installs.

After the one-time setup, installs from unregistered developers can be enabled for 7 days or indefinitely, and an "Install Anyway" warning still appears. A system service, Android Developer Verifier, checks whether an installed app is registered to a verified developer.

What developers must do

Full verification requires an Android Developer Console or Play Console account, identity verification and package-name registration via an APK signed with the developer's private key. Reporting by The New Stack put the standard fee at $25 with a government ID requirement. A free limited distribution tier for students and hobbyists needs no ID and no fee, but caps sharing at 20 devices. Android Studio now shows a registration-status indicator for signed builds.

F-Droid's signature objection

F-Droid, the community repository for free and open-source apps, remains the loudest critic. Its team says linking every app to the developer's registered signing key conflicts with how F-Droid works: it builds about 85% of its catalog from source and signs the result with its own key, and only around 15% of the catalog is reproducible. Google says its analysis found sideloaded apps carry over 90 times more malware than Play apps, without publishing the methodology. A Change.org petition gathered roughly 69,000 developer signatures.