Android verification starts September 30 in four countries. Check the store list.

September 30 is an Android app-verification deadline with a surprisingly specific address. Google's first enforcement phase covers seven app stores in Brazil, Indonesia, Singapore and Thailand. It is not the date when every Android owner worldwide must begin waiting 24 hours to install an APK.

That distinction is getting lost as the new installation controls appear on phones. The controls are real, and the longer-term plan is broader. But Google's current rollout page separates the regional September launch from the expansion to all apps on certified Android devices in 2027. Checking which stage applies is more useful than treating every screenshot as evidence of a worldwide shutdown.

The September phase applies to certified devices running Android 7 or later. Google lists Google Play, HONOR App Market, OPPO App Market, Samsung's Galaxy Store, Palm Store, vivo's V-Appstore and Xiaomi GetApps as the participating stores. Apps distributed through those stores must be registered to verified developers in the four initial countries.

F-Droid is absent from that first-phase list. That does not give it a permanent exemption: Google's implementation guide says the verification capability will expand to other third-party stores, with global coverage of all apps on certified devices planned for 2027. It does mean that describing September 30 as an immediate ban on every F-Droid installation overstates the published rollout.

Google calls its alternative installation route the advanced flow. In his August rollout announcement, Android community engagement manager Mishaal Rahman explained that registered apps can still be installed from websites and other alternative sources without this process. ADB installations and apps shared through limited-distribution accounts are also exempt from the advanced flow.

For unregistered apps, enabling the option involves opening Developer Options, authenticating, answering a question about whether someone is directing you, restarting the phone and waiting 24 hours. You then return to choose permission for seven days or indefinitely. Installation warnings remain. This is a setup delay, rather than a fresh day-long timer attached to every APK download.

There are details worth knowing before relying on it. Rahman says unregistered apps can only be installed or updated while the option is enabled, or through ADB, where verification is enforced. He also says Developer Options can be switched off after setup without undoing the permission. The advanced flow is arriving gradually, so its absence from one phone's settings does not establish that the feature has been cancelled.

Android Authority's September 1 report examined screenshots posted by Reddit user Super-Ad8814. They showed the coercion warning, restart instructions and a remaining-time display. The phone could still be used during the wait. That is evidence of the interface reaching at least one user, not a measurement of how many phones have it or where enforcement has begun.

Google's explanation for the delay is that scammers create urgency and coach victims into weakening their phone's protections. A restart interrupts calls and remote access; the waiting period creates time to reconsider. That is the company's design rationale. The material reviewed here does not establish how effectively this particular sequence prevents scams in practice.

The opposing concern is who gets to control distribution. In its February open-letter announcement, F-Droid argued that requiring developers to register centrally with Google disadvantages alternative stores even when those developers do not distribute through Google Play. Its objection encompasses identity requirements and dependence on Google's terms, not just extra taps during installation.

Privacy channel Techlore explained its own decision to sign the letter in a video from the same period. It argued that independent distribution matters even to people who currently get all their apps from a mainstream store, because it preserves the possibility of competing services. That is an advocacy position, clearly identified as such.

Some predictions in those early objections have been overtaken by events. F-Droid's February post said an advanced flow would not be available before September; Google subsequently began rolling it out in August. A present-day account should correct that timeline while still taking the centralisation argument seriously.

For readers preparing for the deadline, the useful first step is to identify the apps and distribution channels they actually depend on. A verified app downloaded directly from its developer and an unregistered app are different cases. Check the current regional rules before changing settings, and judge any installation warning on the app's origin and behaviour. September's rollout is limited; the decision about Google's future role in Android distribution is much larger.

Image: illustrative Android app screen, not the verification interface. Photo by El Jundi / Pexels, used under the Pexels licence.