Android Isn’t Dying — It’s Already Dead. And We Killed It.

You bought an Android phone because you wanted freedom. You wanted to sideload apps, install a custom ROM, and tweak every setting until it felt like yours. That was the promise: an open platform where you, not some corporation in Cupertino, called the shots.

But here’s the truth no one wants to admit: the open source Android you fell in love with is a ghost.

I saw it happen slowly, then all at once. First came Google Play Services — a closed, proprietary blob that every app started requiring. Then came the kernel update delays. Then the Pixel-exclusive features that could have been AOSP but weren’t. Then the quiet death of custom ROM communities, not because people stopped caring, but because the platform had become so locked down that even the most dedicated tinkerers couldn’t keep up.

And now we’re here: nearly 4 billion devices running Android, but not a single one of them is truly open.

We tell ourselves that Android’s openness is what drove its success. That the fragmentation, the messy ecosystem, the thousand different OEM skins — that was the cost of freedom. But the reality is more uncomfortable. The very success that brought Android to 4 billion devices is what killed the openness that made it desirable in the first place.

Google didn’t plan to kill open Android. They just needed to make it work for everyone — and ‘everyone’ doesn’t want to tinker.

Think about it. Every time you bought a new phone, you lost a little more control. First it was the bootloader lock. Then the inability to install a custom recovery without a fight. Then the apps that refused to run on rooted devices. Then the push for Google’s own services, baked so deep into the OS that removing them broke half the apps you use.

This isn’t a gradual decline. It’s a completed takeover. The Android Open Source Project (AOSP) still exists — a hollow shell maintained for compliance and nothing more. No serious innovation happens there. The real Android lives in Google’s proprietary code, and if you want the latest features, the best security patches, the seamless experience, you play by Google’s rules.

I remember the day I realized it. I was trying to install a custom ROM on a phone that cost $200. The ROM’s developer had given up because the vendor blob drivers were closed, the kernel sources were outdated, and Google’s attestation APIs had made the phone essentially brickable if you tampered with it. The freedom I was chasing was already gone. I had just been too busy enjoying the ride to notice.

So what do we do? We mourn. And then we stop pretending.

Android isn’t dying as an open platform. It’s already dead. The ‘open’ label is a legacy brand, a logo on a tombstone.

If you want real openness, you’ll have to go elsewhere — or build it yourself. But don’t expect Google to hand it to you. They already won. Everyone who bought an Android phone because they wanted freedom voted for the opposite. We wanted the platform to succeed, and in doing so, we ceded control to the one company that could make it succeed at scale. We got what we asked for: a billion‑user operating system that works. And we lost what we really wanted.

The next time someone says Android is open, ask them to list five things they’ve customized that weren’t controlled by Google. Watch them struggle. Then tell them the truth: Android is the most successful closed platform ever sold as open. And we sold it to ourselves.

FAQ

Q: Doesn't AOSP still exist and work?

A: AOSP exists, but it's a museum of old code. Google's real development happens in proprietary services like Play Services, Widevine, and the closed bootloader stack. Without those, a modern Android phone is nearly unusable.

Q: If Android is dead as open, what should developers do?

A: Stop assuming Android is a safe bet for open-source freedom. Build for platforms that are genuinely open (like Linux desktop, Aurora OS, or PostmarketOS) — or accept that you'll be playing by Google's rules.

Q: Is there any hope for an open alternative to Android?

A: Yes, but it won't come from Google. Projects like GrapheneOS and LineageOS keep the spirit alive, but they're limited by hardware blobs and Google's dependency. The real fight is for device manufacturers to provide open drivers — and that fight is mostly lost.

📎 Source: View Source