You probably never think about how an app gets onto your phone. You tap install, it shows up, done. That casual reflex is about to pick up some friction, and the people who feel it first are the ones who grab software the old-fashioned way by pulling a file straight off a website. If you have ever gone hunting for a 1xbet apk or any package that skips the official store, the route you took is getting fenced off.
Google spent the back half of last year sketching out the plan, and the dates are now close enough to matter. Starting in September 2026, Android will only install apps tied to a verified developer on certified devices. The store you tap every day barely changes. What changes is almost everything you install from outside it.
The Quiet Rewrite Of Installs
The headline rule is simple to state and easy to underrate. Every app, including the ones you sideload from a random download page, has to be registered by a developer who proved who they are. Google’s case rests on one number it keeps repeating, that internet-sideloaded sources carry more than fifty times the malware of Play Store apps. The figure traces back to Google’s own analysis, and no outside group has shown its working, which is worth holding in mind before you file it under settled fact.
It does not switch on everywhere at once either. A small set of markets singled out for higher rates of app scams go first, with the rest of the world folded in from 2027.
| When | What changes |
| October 2025 | Early verification sign-ups open |
| March 2026 | Verification opens to every developer |
| August 2026 | The slow install path for unsigned files arrives |
| September 2026 | The verified-developer rule goes live in the first markets |
| 2027 onward | Wider rollout, region by region |
The New Speed Bump On Downloads
Here is where it gets personal. For anything from an unverified source, you will meet a deliberately sluggish path, the sort of menu that makes you abandon an app mid-download rather than sit through it. The first time, there is a 24-hour wait baked in. After that one-time setup you can unlock sideloading for seven days or leave it open for good, so the cost is mostly upfront rather than forever.
Developers carry their own version of the toll. The standard route asks for a government ID, a home address, and a $25 fee through a new console. Students and hobbyists get that fee waived, though their accounts come with caps on how many installs they can push. Reasonable on paper. The catch is that a lone coder shipping a niche tool now has to hand personal paperwork to a company just to put software on a phone they own.
Who Gets Squeezed First
Some categories have lived outside the official store for years, and real-money play is the obvious one. Sportsbook and casino apps run into strict store policies in plenty of places, so operators have long pointed users to a file on their own site instead. That direct-download habit is precisely the behaviour the new system was built around. A verified operator can carry on without much drama, but the casual grab from some mirror page, the thing a lot of bettors got comfortable with, stops being a tap-and-go affair and turns into a few extra hoops.
What You Can Still Do
None of this locks you out. A verified app installs the way it always did, no waiting, no warnings stacked between you and the button. The friction only appears for unsigned files from names Google cannot vouch for, and even then there is a way through for anyone willing to look for it. Power users keep their escape hatch.
The open question sits with the smaller stuff. The one-person projects, the experimental builds, the tools that never went near a verification queue because the author just wanted to share them. Do they cough up the paperwork and the fee, or quietly fall off your phone the next time the rule tightens?