Google’s first Android developer-verification enforcement phase began on September 30, 2026, in Brazil, Indonesia, Singapore and Thailand. It covers apps distributed through seven participating stores, while direct APK sideloading is outside that phase. The United States was not among the four countries, and Google plans a global expansion in 2027. Google’s rollout guide and developer-verification FAQ set out the scope.
Android developer verification links apps to verified developers. It does not require apps to be distributed through Google Play: registered apps can also be distributed through other stores or directly, Google says.
Which devices and stores are covered?
Google says the protections apply to certified Android devices running Android 7 or later, with updates delivered through Google Play services. The first enforcement phase covered apps from Google Play, HONOR App Market, OPPO App Market, Galaxy Store, Palm Store, V-Appstore and GetApps in Brazil, Indonesia, Singapore and Thailand.
The United States is outside that initial phase. Google’s planned global expansion in 2027 is the next stated stage; the initial rollout did not impose verification enforcement on direct APK sideloading.
Advanced Flow and ADB are separate routes
For apps from unverified developers, Google offers Advanced Flow: a one-time setup that introduces a one-day wait. The process involves enabling developer options, confirming that no one is coaching you, restarting the device, waiting 24 hours, reauthenticating and choosing permission for seven days or indefinitely. Google says you can turn Developer Options off after setup without turning off the permission.
Android Debug Bridge (ADB) is a separate installation route. Google says ADB installs are not subject to the Advanced Flow wait, and the ADB workflow remains unchanged. It does not enable the Advanced Flow setting; it provides another route for installing unregistered apps.
| Installation route | Wait | Setup and continuing permission | Installing unregistered apps |
| Advanced Flow | One day for the one-time setup | Enable developer options, confirm you are not being coached, restart, reauthenticate, then choose seven-day or indefinite permission. Developer Options can be turned off afterward. | Available while Advanced Flow is enabled. |
| ADB | No Advanced Flow wait | Use the ADB installation route; it does not switch on Advanced Flow. | Available through ADB. |
What happens to unregistered-app updates?
Google says unregistered apps can be installed or updated only while Advanced Flow is enabled or through ADB. If you turn Advanced Flow off and do not use ADB, those apps cannot be installed or updated. That makes the permission choice practical: indefinite access avoids repeating the setup, while seven-day access expires and requires the flow again when you need it.
What one Android 13 test found
In an account published on October 10, 2026, Gregory Gibson of MakeUseOf described using Advanced Flow on a Samsung phone running Android 13. He reported installing F-Droid and Fossify Calculator, then turning Advanced Flow off and reinstalling F-Droid through ADB; the terminal returned Success. That is Gibson’s result on one device, not a guarantee for every phone or app. Read Gibson’s account.
Gibson also reported checking the F-Droid APK with GnuPG. The check matched the file to the imported F-Droid signing key. A matching signature does not establish Google developer registration or prove that software is harmless.
