Android's 30 September install check is narrower than it looks

On 30 September, an Android phone in four countries starts asking a question it has never asked before: not what this app does, but who made it, and whether that person has told Google who they are.

The change has been reported for the better part of a year as the end of sideloading. It is not, yet. Google's own documentation is unusually specific about the boundaries of what happens next month, and almost everything outside those boundaries carries the word yet rather than never.

What actually changes on the date

Google calls it Android developer verification. A developer registers an identity — and separately registers the package names of the apps it ships — and from the deadline an unregistered app will not install on a covered device.

The coverage is narrow on four separate axes at once:

• Four countries. Brazil, Indonesia, Singapore and Thailand.
• Seven stores. Google Play, HONOR App Market, OPPO App Market, Galaxy Store, Palm Store, V-Appstore and GetApps — Google's blog names the companies behind them as Google, Honor, OPlus, Samsung, Transsion, vivo and Xiaomi.
• Certified devices running Android 7 or higher, with the checks delivered through Google Play services rather than an OS update.
• Phones and tablets. The FAQ says enforcement in the selected regions applies to mobile and tablet form factors; a developer shipping on Play has to register across all form factors regardless.

Everything after that is 2027, and 2027 is all Google has said. The landing page's own timeline reads: August 2026 for the developer APIs, limited distribution accounts and the advanced flow; 30 September 2026 for the regional deadline; then “2027 and beyond” for the global rollout to all certified Android devices. No month, no ordering of markets.

The part most coverage gets backwards

If you install a game by downloading the file from the developer's own site, next month changes nothing for you. That is not an inference — it is an FAQ answer, dated 15 July 2026, to the question of what happens if you sideload your app or distribute it through a store that is not on the list.

Elsewhere the same page answers the question of whether Android is becoming a closed system with a flat no, and lists direct website downloads among the channels developers may continue to use. That answer is dated 18 June 2026 and it is worth reading with the last clause of the previous one still in mind. The requirement is not being lifted from sideloading. It has not arrived there.

It is about updates too, not just first installs

This is the detail worth carrying away if you keep anything on your phone that did not come from a store. Two FAQ answers, both dated 25 March 2026, say the same thing from opposite directions: unregistered apps can only be installed or updated when the advanced flow is enabled or when using ADB, so with the advanced flow switched off, updates to an unregistered app will fail.

An app that stops updating does not announce itself. It sits there working until the day a server change or an OS update leaves it behind, and by then the reason is months old. If you are in one of the four countries and you have a game installed from outside the participating stores, the thing to check after the deadline is not whether it still opens — it is whether it still updates.

The advanced flow, and why you cannot do it in a hurry

Google's answer for people who want to install from unverified developers anyway is a one-time setup it calls the advanced flow. The FAQ sets out the steps:

1. 1

   Enable developer mode in system settings

   Google's stated reason is that this prevents accidental triggers and the one-tap bypasses used in high-pressure scams.

2. 2

   Confirm you are not being coached

   A check that nobody is talking you into turning off your security.

3. 3

   Restart the phone and reauthenticate

   Described as cutting off any remote access or live call a scammer might be using to watch what you are doing.

4. 4

   Come back after the waiting period

   A one-time, one-day wait, then confirmation by fingerprint, face unlock or device PIN. Google's stated reasoning is that scammers rely on manufactured urgency, and the 24-hour pause breaks it.

5. 5

   Install

   You can enable it for seven days or indefinitely. You still get a warning that the app is from an unverified developer, with an Install Anyway option.

The practical consequence of step four is a scheduling one. If a game you follow is distributing something you need to sideload — a build for a launch, a version your store does not carry — the setup cannot be done on the day. It is once per account rather than once per app, and Google says it carries over to a new device, so it is a thing to do calmly in advance or not at all.

The exemptions, because they say what the rule is for

• ADB is untouched. Installing over Android Debug Bridge needs no registration and the 24-hour wait does not apply to it. Modifying an APK and installing it on your own device is covered by the same answer.
• Managed devices are out of scope. Apps distributed through an organisation's own store on managed devices do not need to meet the requirements, on the basis that an IT admin has already vetted them.
• Hobbyists get a free tier. Limited distribution accounts, launching globally this month, let a developer share an app with up to 20 devices with no government ID and no fee. A full distribution account on the Android Developer Console costs $25, which Google compares to Play's registration fee.
• Sanctioned countries are excluded from the verification checks entirely, which Google notes also means users there do not get the protection.

Taken together those carve-outs describe the target fairly precisely: not enthusiasts, not enterprises, not students, but anonymous mass distribution to ordinary users through stores. Whether identity checks stop that is a question this article cannot answer. What they change for you is knowable, and it is mostly a matter of which of the four countries you are in and where your games come from.

What to do before the end of September

If everything you play came from Google Play or one of the other six stores, nothing. Google's position is that most users will see no change at all in how they download apps, and that is the likeliest outcome for anyone whose install history is a list of store pages.

If you are in Brazil, Indonesia, Singapore or Thailand and some of your games did not come from a store, the useful preparation is an inventory: which ones, from where, and whether each one updates itself or expects you to fetch the next file yourself. The ones that update themselves are the ones with a deadline you did not set.

And if a game vanishes from Google Play in the next few weeks in a country nowhere near this rollout, the registration deadline is now a reasonable first suspicion rather than the mystery it would have been in August. For what happens to what you have already bought when a game does go away for good, we have written that up separately in what happens to your account when a mobile game shuts down; for the other direction Google has been pushed in this year, when a game asks you to pay on its own website instead covers alternative billing on Android.