Google Is Quietly Closing Android, and 37 Groups Are Fighting Back

You bought the phone. Google decides what runs on it. That’s the trade Android users will face starting in 2026, when Google’s new developer verification rules take effect — and it’s why 37 advocacy groups, open-source projects, and privacy organizations have banded together under a single banner: Keep Android Open.

The freedom that defined Android

Sideloading — installing an APK without going through the Play Store — has been Android’s defining feature for over a decade. It’s the line that separated Google’s platform from Apple’s walled garden. You could grab an app from a developer’s website, install F-Droid, run a build a friend sent you on Discord. That openness wasn’t a bug. It was the pitch.

Under the new policy, every Android developer must register with Google and pass identity verification before their apps can be installed on consumer devices. Inside the Play Store or outside, it doesn’t matter. Unverified apps get blocked at the OS level. Google insists sideloading “still exists.” In practice, the verification gate is the new gatekeeper.

A YouTube backlash that became a coalition

When Louis Rossmann posted his takedown in August 2025 — bluntly titled “Google: you need our permission to install apps on your $1,000 phone” — it racked up 620,000 views and 73,000 likes. The comments read like a wake. Then Techlore’s February 2026 explainer, “Google is closing Android — and 37 groups are fighting back,” pulled another 430,000 views.

This isn’t one creator venting. F-Droid, the EFF-adjacent privacy crowd, and a long list of indie developer collectives signed onto a joint statement. The Hacker News threads have been brutal; the r/Android response, surprisingly unified for that subreddit. The phrase “Android is the new iOS” keeps surfacing, and it’s not meant as a compliment.

Google’s case, and the part it isn’t saying

The official rationale is security. Banking trojans spread via sideloaded APKs are a real, ongoing problem, especially in regions where alternative app distribution is the norm. Verifying developer identity, Google argues, makes attribution possible and raises the cost of malware distribution. That’s not nothing.

The side effects are where it gets uncomfortable. Anonymous developers — common in the privacy and activism space — now have to expose themselves to a US corporation. Hobbyists who never planned to monetize face the same paperwork as commercial studios. And whoever holds the verification button effectively holds a veto over what gets to exist on the world’s largest mobile OS. Ad blockers, emulators, jailbreak utilities, scraper tools: how many survive a process where Google decides who’s “legitimate”?

The EU is going the other way

Here’s the irony nobody at Mountain View wants to dwell on. The Digital Markets Act forced Apple to crack iOS open in Europe — alternative app stores, sideloading, third-party browser engines. Apple is opening up under regulatory pressure. Android, the supposedly open platform, is closing down voluntarily. If both trends continue, the practical difference between the two ecosystems collapses to a logo on the back.

For developers, the operational pain is real. Register with Google, pass KYC, comply continuously, and accept that policy violations can revoke your verification. Get blacklisted once and you’re not just removed from the Play Store — you’re locked out of the Android app economy entirely. The old promise that a developer could hand an app directly to a user becomes a permission Google grants and revokes.

Whose phone is it, anyway?

You can read this as Google hardening a malware-ridden ecosystem, or as the mobile duopoly closing the last gap that made one option meaningfully different from the other. Both readings are defensible. What’s no longer defensible is the casual claim that Android is “the open one.”

When you buy a phone, you think you’re buying hardware. Increasingly, what runs on top of it is governed by terms you didn’t sign and can’t negotiate. After 2026, “is this phone really mine?” stops being a rhetorical question — and starts being a product category waiting for someone to build it.