Updated August 2026 · Google's verification pages, FAQ and console help re-read on 18 August 2026, along with F-Droid's own posts and the Keep Android Open open letter
Nothing changes for most readers on 30 September because Google's developer verification page, read 18 August 2026, limits that deadline to seven named stores in four countries. Direct sideloading is untouched for now because Google's own FAQ, read 18 August 2026, says the requirements will not apply yet to apps users sideload directly. ADB is untouched because Google's FAQ, read 18 August 2026, says the waiting period does not apply to ADB installs. Data checked: 18 August 2026.
The next date on Google's schedule is 30 September 2026, and it is narrower than the coverage suggests: seven named stores, four countries, certified devices. This page sets out what changes on each way of installing an app, what Google has actually published about the rest, and where its own pages disagree with each other. The related change to who may download an app at all is covered in our guide to Google Play age verification.
Most people, most apps
Google's developer verification page and its FAQ · read 18 August 2026 · source
If you install from Play and you are not in one of the four named countries, nothing about 30 September concerns you. If you are, the change happens on the developer side and Google says the download itself does not feel different for apps whose developer has registered.
Skip it if you are outside Brazil, Indonesia, Singapore and Thailand, because nothing on this route changes for you next month. Choose it over every other route if convenience is the goal, since it is the one route where the reader does nothing at all.
Betas and direct downloads
Google's developer verification FAQ, answer stamped 18 June 2026 · read 18 August 2026 · source
This is the sentence that decides the whole subject, and it is the one most coverage skipped. Google states that the September deadline does not reach apps that people install directly at all.
Skip it if nothing, on this route, before 2027. Choose it over a store when you want a build the store does not carry, since Google has left this path open in the current phase.
Power users, later
Google's FAQ, answers stamped 23 March, 11 May and 8 June 2026 · read 18 August 2026 · source
The route Google documents for keeping unverified apps installable, deliberately slow and deliberately awkward. Read the status before the steps: Google schedules it for August 2026, and on the day this page was checked it had not been confirmed as shipped.
Skip it if you can get the same app from a developer who has registered, because this route costs a day of waiting the first time. Choose it over giving up on an app if you rely on software from developers who will not register, and do the setup on a calm day rather than the evening you need it.
Galaxy, Xiaomi, OPPO owners
Google's developer verification guides · read 18 August 2026 · source
The comforting line that alternative stores keep working is true and, on its own, misleading. Six of the seven stores in the first enforcement phase are alternative stores, so for a lot of readers the change arrives through exactly the shop they were told was unaffected.
Skip it if you are outside the four countries, because the enforcement is regional before it is global. Choose it over a downloaded APK when the store carries the app anyway, since a store handles updates that a manual download does not.
Open source catalogues
F-Droid's own post of 29 September 2025 and the Keep Android Open open letter · read 18 August 2026 · source
F-Droid is not among the seven participating stores, so nothing about 30 September reaches it. What is unresolved is 2027, and the dispute is structural rather than rhetorical: F-Droid builds apps from source and signs them itself, so there is often no registered developer standing behind the file you install.
Skip it if nothing today, since this route is untouched in the current phase. Choose it over a participating store if you want software built from published source, while watching what happens to the 2027 step.
People with a cable
Google's FAQ, answer stamped 23 March 2026 · read 18 August 2026 · source
The clearest answer on the whole subject, and the one worth knowing if you install things the hard way. Google was asked directly whether the waiting period touches ADB, and answered in three short sentences.
Skip it if you are not comfortable at a command line, because everything here assumes one. Choose it over the advanced flow when you already have the tools set up, since Google exempts it from the waiting period entirely.
What has passed, and what has not
Google publishes a milestone table on its verification landing page, and reading it against today's date is the fastest way to see where this actually stands. Read 18 August 2026:
One date has been removed from this page. It previously said the Android Developer Verifier service started appearing on phones in April 2026. Google's post of 30 March 2026 planned that step, and no Google page read on 18 August 2026 confirms it happened, announces a delay, or mentions April again. Since Google is silent rather than contradictory, neither "it happened" nor "it slipped" can be written, so the claim is gone. The service itself is real and named: Google's consumer help page identifies it as Android Developer Verifier, package name com.google.android.verifier.
What registration costs
The part that decides how many apps survive this is what registration costs the people who write them. Google publishes two tiers on its Android Developer Console help page, read 18 August 2026.
Google frames the requirement itself as an identity check rather than a review, and states plainly on the same page that verified developers keep the freedom to distribute directly or through any store they prefer. Whether that is enough is the argument the open letter is having, and it is a real argument rather than a misunderstanding: a project that builds and signs other people's software does not have an obvious place in a scheme built around registering individual developers. If you want to see which storefronts this reaches, our roundup of the best app store apps for Android covers the main ones.
Where Google contradicts Google
Two of Google's own pages disagree, and both disagreements are worth carrying rather than smoothing, because a reader who checks will find them.
What is settled is the exemption. Google's consumer help states it in one line: "Requirements apply only to Certified Android devices. Android Open Source Project (AOSP) and non-certified devices are exempt from this requirement", and adds that the requirement does not apply where Google Mobile Services are unsupported or in territories under trade sanctions.
So the practical list for a reader is short. If you are outside Brazil, Indonesia, Singapore and Thailand, nothing happens to you next month. If you are inside them, the change reaches you through a store rather than through a download. Either way, take APKs from the developer's own site rather than a mirror, because verification proves who someone is and not what their app does. And if command-line installs are already part of how you use a phone, our guide to the best root apps for Android covers the neighbouring territory.
No. Nothing in what Google publishes removes or disables an app you already have. The deadline is about installing and updating apps from seven participating stores, in Brazil, Indonesia, Singapore and Thailand, on certified devices. Outside those countries nothing changes next month at all. Checked 18 August 2026.
Yes, and this is the part most coverage got wrong. Google's own FAQ says the 30 September deadline applies only to the specific participating stores, and that where users sideload an app directly the new requirements do not apply yet, with install experiences unchanged in September. Google's console help puts the principle more bluntly, saying sideloading is fundamental to Android and is not going anywhere. The route does change in the 2027 global step. Checked 18 August 2026.
No. F-Droid is not one of the seven participating stores, so the September deadline does not reach it, and it was publishing app updates as normal in August 2026. What is unresolved is 2027, when Google says the requirement expands to all apps on certified devices. F-Droid's published objection is that it cannot take over the application identifiers of the open source apps it distributes, because doing so would seize exclusive distribution rights over them. Checked 18 August 2026.
Neither. Google describes the advanced flow as a one-time setup: users complete it once per account and it carries through to a new device, rather than being repeated for each app. After it, you choose whether installs from unverified developers stay enabled for 7 days or indefinitely, and a warning still appears at each install that you can accept. Checked 18 August 2026.
No. Google frames this as confirming who the developer is rather than reviewing what the app does or where it came from. That is worth holding onto in both directions: a registered developer is traceable if they ship something harmful, which is real deterrence, but registration is not an inspection and not a safety rating. Checked 18 August 2026.
Only indirectly, and only in the four named countries for now. The work falls on developers, and Google says the download experience does not change for apps whose developer has registered. The one effect you might notice is absence: an app whose developer never registers is one you will not find on that route in those countries. Checked 18 August 2026.
Checked 18 August 2026: the page's central claim was wrong and has been rebuilt around what Google publishes. It said that from September 2026 an app must be registered before it can be installed or updated on a certified Android device. Google's own FAQ, in an answer stamped 18 June 2026, says the opposite about the route this page is named after: the 30 September deadline "only applies to the specific participating stores", and for apps users sideload directly the requirements "won't apply to your app yet", with install experiences unchanged in September. The date itself is 30 September 2026, not September generally, and the first phase is bounded by store as well as by country: seven stores, of which six are alternative stores, so the reassurance that alternative stores keep working needed the other half of the sentence. The 2027 step has been restated too, because Google describes it as expanding to all apps on certified devices rather than simply to more countries. The claim that the Android Developer Verifier arrived on phones in April 2026 is removed: Google planned it in March and has published nothing since confirming it, so neither the event nor a delay can be asserted. On the opposition side, the open letter is published by the Keep Android Open campaign with F-Droid as a signatory, not published by F-Droid, and it carries 71 organizations from 23 countries; F-Droid's actual argument is about application identifiers rather than about registering on behalf of volunteers, and it is now quoted in its own words. Smaller corrections: Google says reauthenticate rather than sign in again, describes enabling installs "for 7 days or indefinitely" without saying the window renews, ties the one-time setup to the account rather than to a restore, and answers only that an ADB bypass "is not supported at this point". The $25 full account fee and the free limited distribution tier are now stated with their source. A decision table, an "Our answer" capsule, a dated verification box and this changelog are new, and the page now prints the two places where Google's own pages contradict each other.
The Best Password Manager Apps for Android (2026)Security & Privacy
Google Play Store Not Working or Won't Download AppsTools & Utilities