The gatekeeper got a deadline

The European Commission ruled this month, under the Digital Markets Act, that Google has to open Android to rival AI assistants and share anonymised search data with competitors. The specifics are concrete. Google must open 11 Android features to competing AI providers. Users will be able to fire up a third-party assistant with a voice command, the same way they say "Hey Google" today. Search data sharing with eligible rivals starts in January 2027, and the Android changes reach users from July 2027.

Google pushed back hard, warning about privacy, device security, and national security risks. That objection is worth taking seriously. But strip away the legal framing and there is a plain signal here for anyone building an AI product. The default slot is being pried open, and defaults were never a strategy you owned anyway.

Being the default is borrowed distribution

Plenty of AI products have quietly built their growth model on being pre-installed, pre-selected, or wired in as the assistant that answers when someone holds a button. It works right up until the platform owner, or a regulator, changes the rules. Then the traffic you treated as yours turns out to have been on loan.

That is the real lesson in this ruling. When distribution depends on a gatekeeper's choice, your roadmap is partly written by someone else. The EU is opening Android because Google's control of the default was itself the problem. The same dynamic that regulators are now unwinding is the dynamic some builders are betting their acquisition numbers on.

If a policy change or a contract renegotiation can wipe out a chunk of your users overnight, that is not a growth channel. It is exposure.

Build for the switch, not the slot

The upside cuts both ways. Interoperability that forces Google to let rivals in is the same interoperability that lets your product become the one a user actually chooses. Voice-activated third-party assistants on Android is a door opening, not just for the incumbents being reined in, but for everyone who was locked out.

So build for a world where users can swap assistants as easily as they change a keyboard. A few things that actually matter when the default stops protecting you:

Own the relationship, not the placement. Accounts, data portability, and a reason to come back that does not depend on being pre-selected.
Make switching to you trivial. If the platform now allows a third-party assistant by voice, the product that nails that first-run moment wins the habit.
Design for portability. Assume the surface you live on will change its terms. Keep your core logic and data independent of any single platform's API.
Earn the default through quality. When the slot is contestable, the only durable way to hold it is to be genuinely better, not just first.

The shift underneath

Regulators are turning platform defaults into something users pick rather than inherit. That reframes distribution as a product problem instead of a partnership problem. Teams that saw defaults as permanent will feel this as a threat. Teams that always assumed the ground could move will treat it as an opening.

We are here to help founders and teams design and build digital products that are built to scale with you, not slow you down. If you are looking to build something, get in contact with us today.