Play Services is where Android really ships now, and you can't see it

When was the last time you read the release notes for Android? Now try the same question for Google Play services. If the second answer is "never," you're in the majority, and that's precisely the problem.

Find Hub shows why. The full rebrand from Find My Device rolled out through Google Play services version 25.20.37, according to Android Central, citing 9to5Google. More recently, Android Authority describes Google's October System Services update as making Find Hub trackers easier to identify, set up and manage, thanks to new NFC support.

We'll be careful here: the documentation we have is thin on the exact contents of these updates, so we won't pretend to list a changelog. What it does show is a pattern, and the pattern matters more than any single toggle.

The feature list lives in a place with no version number you care about

A rebrand of a feature that appears in Android Settings arrived through Google Play services, not through a new Android version. A tracker-setup improvement arrived through a System Services update. Meanwhile, Google's own support pages already treat Find Hub as something that spans phones, Fast Pair accessories and even Android XR devices. That's a platform feature in everything but name, and it is delivered the way a background service is.

Our view: this is the real Android release cycle. The annual OS number is the marketing event. The store-delivered layer underneath is where a growing share of what you actually use gets changed, and almost nobody tracks it.

Faster delivery is a genuine win, and we won't pretend otherwise

There's a fair defense. A tracker feature that has to wait for a yearly OS upgrade is, in our view, a feature that many phones will never see. Pushing it through the services layer probably means a handset from a brand that's slow with updates can still get improvements like easier tracker setup. For anyone who has watched a perfectly good phone get stranded on old software, that's a real improvement, and people who lean on tags and accessories likely benefit most.

So we aren't arguing the model is bad. We're arguing it's hard to hold accountable.

Invisible delivery means invisible decisions

The best illustration in our documentation isn't about trackers at all. Android Police reports that Google announced DNS-over-HTTP/3 for Private DNS on July 19, 2022, delivered through a Google Play system update for Android 11 and above. It was meant to replace DNS-over-TLS only for well-known servers, with Google and Cloudflare named at launch. The piece says Google rejected a request on its issue tracker in January 2025 to open it to any server. The result, as the author describes it, is that dns.google gets a backup path on restrictive networks that AdGuard DNS and other providers don't.

That's one writer's analysis, and he says himself that he doesn't think Google set this up on purpose to hurt ad blockers. But it shows what a service layer allows: a meaningful networking behavior that differs depending on whose server you type, rolled out in a way that gives ordinary users little say. To us, that's the real cost of the model. When features live in a layer without a visible version number or a headline release, scrutiny shrinks, and so does your leverage as a user.

What to do about it

Practically, three things. First, treat Play services as part of the operating system when you judge a phone's software support; a brand's promised OS years are only half the story. Second, if you rely on Find Hub for earbuds, tags or an XR headset, check its settings after updates, because names and options can shift under you. Third, if you use a non-Google DNS provider, test it on restrictive Wi-Fi before you need it.

And for Google, the ask is simple: publish readable, specific notes for these updates, and say plainly when a feature favors its own services. Android's best features increasingly arrive through a door nobody watches. We'd like a window on it.