In this article
Last updated: 2026-08-31. This story is still moving. I'll keep this page current as Google's rollout continues; the update log is at the bottom.
Starting September 30, 2026, Android will begin checking whether the apps you install come from a developer who has verified their identity with Google. The first phase applies in four countries: Brazil, Indonesia, Singapore, and Thailand, with a global rollout planned across 2027.
Here's the short version. If you install apps from Google Play, nothing changes for you. Play developers have been through identity verification since 2023. If you install apps from outside Play, from F-Droid, GitHub releases, or direct APK downloads, this change is aimed squarely at you: apps from unregistered developers will no longer install through the normal flow on certified Android devices in the affected countries. Sideloading survives this change, with a gate in front of it.
Several well-known launchers are distributed partly or entirely outside the Play Store. This page covers what's changing, which launchers are affected, and what you can actually do about it.
What's actually changing
Under the new requirements, every app installed on a certified Android device (which is nearly every Android phone sold outside China) must be tied to a developer who has registered with Google. There are two kinds of account, and the difference matters more than most coverage suggests.
A Full Distribution account is the one that applies to any app meant for the public. It requires a legal name, address, email, and phone number; a government ID check for individual developers, or a D-U-N-S number for organizations (which is free but can take up to 28 days to obtain); registration of the app's package name and signing keys; and, for developers who distribute outside Play, a one-time $25 fee.
A Limited Distribution account is free, requires no government ID, and exists explicitly for students, teachers, and hobbyists. The catch is the cap: 20 devices. It covers classroom projects and personal builds, not public releases. You can upgrade a limited account to a full one later, but not the reverse.
Google's stated reasoning is malware reduction. It says it sees over 50 times more malware from internet-sideloaded sources than from Google Play, though it has never published the analysis behind that number, and F-Droid has noted that "50 times" is a suspiciously round figure for a claim carrying this much policy weight.
Critics, including much of the open-source community, point out that identity verification does nothing to stop a verified developer from shipping bad code. The free limited tier does take the edge off the most sympathetic case, the student or hobbyist tinkering at small scale. What it doesn't touch is the case the open-source world actually cares about: maintainers who publish to the public, for free, under a pseudonym, and who are unwilling to hand a foreign corporation a government ID and a home address as the price of doing so.
Both things can be true. This page isn't here to referee that argument; it's here to tell you what happens to your apps.
The timeline
| When | What |
|---|---|
| August 2025 | Google announces the developer verification requirement |
| October 2025 | Early access to the verification system opens |
| March 2026 | Registration opens to all developers (Android Developer Console) |
| June 2026 | The verification system service rolls out to devices via Google System Updates |
| July 2026 | The Developer ID Status API goes global; early access to limited distribution accounts opens |
| August 2026 | Limited distribution accounts and the Console API launch worldwide; the advanced flow begins rolling out |
| 2026-09-30 | Enforcement begins for users in Brazil, Indonesia, Singapore, and Thailand |
| 2027 | Global rollout to certified Android devices begins |
Who is affected, and who isn't
Not affected: anything you install from Google Play. The same goes for the other participating stores, which now number seven: Google Play, the Samsung Galaxy Store, Xiaomi's GetApps, vivo's V-Appstore, the OPPO App Market, the HONOR App Market, and Transsion's Palm Store. Those developers are already verified. Your existing apps also don't vanish; this applies to installs, not to apps already on your phone.
Affected: apps from developers who don't register. In the enforcement countries, installing an unregistered app through the normal tap-the-APK flow will be blocked. Two paths remain: the "advanced flow," which Google began rolling out to devices in August 2026, and installation via ADB from a computer. Power users keep an escape hatch; casual users effectively don't.
The advanced flow is deliberately slow, and it's worth knowing what you're signing up for before you need it. You open Developer Options, turn on "Allow apps from unverified developers," authenticate with your screen lock, confirm that nobody is pressuring you into the change, restart your phone, and then wait 24 hours. After that you return to the setting, verify with biometrics, and choose whether to allow unverified installs for seven days or indefinitely. Even then, each install shows an "unverified developer" warning you have to dismiss. The waiting period isn't an accident: it's aimed at scammers who talk victims through sideloading in real time, and it works by making that conversation impossible to finish in one sitting.
The open question for every app distributed outside Play is simple: will its developer register? For some, it's paperwork and $25. For others, it's a real problem. In February 2026, F-Droid published an open letter opposing the requirement, co-signed by the EFF, the Free Software Foundation, FSFE, the Tor Project, Proton, KDE, LineageOS, Nextcloud, Vivaldi, and the Software Freedom Conservancy; by May 2026 it had 71 organizations across 23 countries behind it and over 100,000 petition signatures. Their argument is that centralizing developer identity with Google creates both a surveillance dataset and a pressure point for governments, and that the burden falls hardest on developers in places where handing a foreign company your ID carries real legal risk. Whatever you think of the policy, those developers built much of what makes Android worth using, and they deserve better than being treated as collateral damage.
Where popular launchers stand
The table below reflects each launcher's distribution channels as of 2026-08-31. Whether an outside-Play launcher is affected in the enforcement countries depends on one thing nobody can answer for its developer: whether they choose to register.
| Launcher | Distributed via | What that means |
|---|---|---|
| Nova Launcher | Google Play | Unaffected |
| Niagara Launcher | Google Play | Unaffected |
| Smart Launcher | Google Play | Unaffected |
| Before Launcher | Google Play | Unaffected |
| Microsoft Launcher | Google Play | Unaffected |
| Olauncher | Google Play + F-Droid | Play installs unaffected; F-Droid installs depend on developer registration |
| KISS Launcher | Google Play + F-Droid | Play installs unaffected; F-Droid installs depend on developer registration |
| Lawnchair | Google Play (stable) + GitHub builds | Play installs unaffected; GitHub/nightly installs depend on developer registration |
| Kvaesitso | F-Droid + GitHub only (no Play listing) | Normal installs in enforcement countries depend on developer registration; otherwise advanced flow or ADB |
| Tree Launcher | Google Play | Unaffected |
What you can actually do
If you're outside Brazil, Indonesia, Singapore, or Thailand: nothing changes yet. The global rollout begins in 2027, and the details may evolve before it reaches you. Bookmark this page or the coverage below.
If you're in an enforcement country and rely on sideloaded apps:
- Check whether the app is also on Google Play or another participating store; installing from there sidesteps the issue entirely.
- Set up the advanced flow before you urgently need an app, not during. It's rolling out to devices now, and the 24-hour waiting period means it is useless as a same-day solution.
- ADB installation from a computer remains available and unrestricted.
- Watch the app's own channels (GitHub, F-Droid page) for the developer's decision on registration; many are announcing their plans.
If you care about the open-source ecosystem this lands on: the most useful things are unglamorous. Support the projects you rely on, follow F-Droid's updates on the situation, and make your feedback heard through Google's official channels rather than only in comment sections.
Frequently asked questions
Is Google banning sideloading on Android?
No. Sideloading remains possible. What changes is that apps from unregistered developers won't install through the normal flow on certified devices in enforcement countries; the advanced flow and ADB remain available.
Will apps I've already installed stop working?
Apps already on your device are not removed by this policy. The requirements apply to installation.
Does this affect apps from the Play Store?
No. Play developers have been identity-verified since 2023. The same goes for the six other participating stores, including the Samsung Galaxy Store, Xiaomi's GetApps, and the OPPO App Market.
When does this reach my country?
Enforcement starts in Brazil, Indonesia, Singapore, and Thailand on September 30, 2026, with a global rollout across 2027. Exact timing for other countries hasn't been announced.
Which launchers are affected?
Launchers distributed only through Google Play are unaffected. Launchers distributed through F-Droid or GitHub, including Kvaesitso and the community builds of Lawnchair, depend on whether their developers register. See the table above.
What do developers have to provide to register?
For a Full Distribution account, the kind you need to release an app publicly: legal name, address, email, phone number, a government ID check (or a D-U-N-S number for organizations), registered package names and signing keys, and a one-time $25 fee for distribution outside Play. A Limited Distribution account is free and skips the ID check entirely, but it's capped at 20 devices, so it's for students, teachers, and hobbyists rather than public releases.
Try Tree Launcher
A launcher and a productivity workspace in one. Free on Google Play, and unaffected by these requirements.
Get Tree LauncherUpdate log
- 2026-08-31 โ First published. Covers the advanced flow rollout that began in mid-August 2026 and the worldwide launch of limited distribution accounts.
Sources: Google's developer verification documentation, the Android Developers Blog, and the open letter opposing developer verification.
Tree Launcher is a minimalist Android launcher that organizes your home screen as a tree of pages. It's distributed on Google Play and is not affected by these requirements. If you're weighing your options, I also wrote a full guide to minimalist Android launchers in 2026.