Why I Left GrapheneOS for an iPhone

Let me say this up front: GrapheneOS is a top-tier project. It’s the most private, most hardened phone OS you can run, the team behind it is excellent, and I agree with just about everything they stand for. I ran it for years, and I still recommend it.

And I switched to an iPhone anyway. Here’s the honest reasoning.

The notification problem

The catch with any de-Googled Android is push notifications. Most Android apps deliver them through Firebase Cloud Messaging — Google’s service — so no Google means no notifications. GrapheneOS handles this about as well as anyone can: it lets you install Google Play Services in a sandbox, stripped of the special privileges it holds on a stock phone. It’s genuinely clever work.

But step back and look at what that means day to day. GrapheneOS is at its best when your app list is short and open-source — and that isn’t my life. I need enterprise apps for work, plus plenty of everyday apps that aren’t fully open-source, and the moment you want reliable notifications from those, Google’s telemetry starts creeping back in through Play Services. To get the alerts I actually depended on, I was running Google’s code anyway — just in a nicer box. After a few years, the math stopped adding up: I was carrying all the friction of a de-Googled phone while keeping Play Services on to make it usable. The privacy win had quietly shrunk to something smaller than the effort.

Privacy you don’t use isn’t worth much

That’s really the whole point. GrapheneOS is more private than an iPhone in absolute terms — I won’t pretend otherwise. But privacy that costs enough friction that you keep bolting the compromises back on isn’t buying you as much as the spec sheet claims.

A modern iPhone, by contrast, is genuinely private for the average person right out of the box, and with the settings tuned — ad tracking off, Advanced Data Protection on, location kept on a short leash — it gets seriously good. Not GrapheneOS-good. But good with none of the daily tax.

There’s also a whole category of everyday convenience that de-Googled Android simply gives up. Contactless payments are the clearest example: they don’t work on GrapheneOS at all, while Apple Wallet does — and about as privately as mobile payments get. Apple tokenizes your card and doesn’t build a profile of what you buy, which is more than Google’s or Samsung’s wallets can claim. Smaller professional touches land the same way: a proper contact card with my photo for caller ID, or tapping a phone to share details cleanly in a meeting. None of it is earth-shattering, but it’s exactly the private-by-default polish that makes a phone something you use instead of fight.

It comes down to who’s selling what

Here’s the part that settled it: incentives. Apple makes its money selling hardware. Google makes its money selling ads, which means selling a profile of you. That difference shows up everywhere. Sign into a Google account and it keeps a running log — your searches, your YouTube history, your location if you let it — all viewable in a dashboard most people never open, and much of it switched on by the time you finish setup. Apple simply doesn’t keep the same ledger, so there’s no such dashboard to find.

I won’t pretend Apple is a charity. It collects telemetry too, and it runs an ad business you should still switch off. The difference is intent: Apple’s data goes toward improving its own products, while Google’s entire model is to package your behavior and sell access to it. Same word — telemetry — opposite purpose. And that changes what the defaults are built to do.

So my line isn’t really Android versus iOS — it’s Google. I keep Google’s services and apps off my phone and out of my life wherever I can, because to me Google is, first and foremost, an advertising company that happens to make software. On an iPhone, staying off Google is easy. In the end, that was worth more to me than the last few percent of hardening I gave up.