Brussels pulls the lever on Android, putting Google's AI defaults in the crosshairs

Brussels dropped its latest platform shot on 17 July 2026, when the European Commission told Google to make Android a more hospitable home for competing AI assistants. The instrument is the Digital Markets Act, the bloc's 2022 rulebook for the largest digital gatekeepers, and the target is the most contested piece of real estate on the device: the assistant that answers when a user holds down the home button or types into the default search bar.

The Commission's case is straightforward on paper and politically combustible in practice. Android, the operating system running on the majority of the world's smartphones, ships with Google services stitched in at the platform level. For years, third-party assistants from the likes of OpenAI's ChatGPT and Perplexity have had to negotiate that seam one handset maker and one distribution deal at a time. Brussels is now arguing that seam is a chokepoint, and gatekeepers are not allowed to run it for their own benefit.

This publication's read is that the order matters less for what it technically forces on Android than for what it confirms about the direction of travel. Brussels has spent four years converting the DMA from text into operating pressure on Apple and Google, with App Store rules, browser choice screens, and payment-stack fights already on the books. Reaching inside the OS to decide which AI gets the prime button is a step deeper into the device, and the Commission's appetite for that fight is the real story.

What the order actually changes

The Commission is invoking the DMA's interoperability and anti-self-preferencing provisions to push Google toward a model in which users see and can pick rival assistants with the same prominence as Gemini. The substantive lever is default status: under EU rules, a gatekeeper cannot use its platform position to favour its own auxiliary services, and defaults are the clearest expression of that favouritism. If a user wants ChatGPT or Perplexity to answer a voice prompt, they should not have to dig two menus deep to find it, the argument runs.

Implementation will turn on details that Brussels has not yet finalised. The Commission will need to define what prominence looks like on a Pixel, a Samsung, a Xiaomi. It will need to settle whether the rival assistants get a one-shot setup prompt, a persistent badge, a slot in the power-button menu, or all three. And it will need to draw a line between operating-system-level integration and the kind of first-party Google app that ships with Android regardless of what users want.

Google's options narrow from there. The company can comply, drag its feet and absorb fines, or challenge the interpretation in court. The DMA grants the Commission powers to fine up to ten per cent of global turnover for breach, rising to twenty per cent for repeat offences, and to impose structural remedies in extreme cases. Those numbers were written precisely for firms with Google's balance sheet.

The counter-narrative from Mountain View

Google's defence, as telegraphed in earlier DMA proceedings, runs on three lines. First, that Android is already open: any user can install a rival assistant from an app store, and any handset maker is free to ship with a different default. Second, that deep integration between an OS and its first-party assistant produces the kind of on-device performance and privacy guarantee users want, and that forcing a generic plumbing layer risks degrading both. Third, that the Commission is reaching past competition policy into product design, a move Google frames as politicians deciding which buttons belong where on a consumer device.

That case is not frivolous. The performance and privacy argument has technical merit; the counter to it is that consumers cannot evaluate those trade-offs when the alternative is hidden behind a settings toggle. The product-design argument has a foothold in US commentary too, where the DMA is routinely characterised as European industrial policy dressed in competition-law clothing. That framing is not wrong, exactly, but it elides the question of whether a platform with roughly seven out of ten smartphones worldwide gets to decide defaults unilaterally.

Why this fight is about AI, not just search

The DMA's earlier flashpoints, browsers, app stores, payment stacks, were about money paths: who gets the click, who takes the fee, who controls the checkout. The Android assistant fight is different in kind. Voice and generative assistants are not commodity inputs that can be swapped on price. They are brand experiences built on proprietary models with proprietary training stacks. Slot one assistant into the power-button position and you are not just changing a default. You are shaping which model a user reaches for first, which is the single most predictive variable in any AI company's funnel.

That is why the assistant category has drawn a sharper regulatory response than generic search ever did, even though the underlying gatekeeper is the same. Brussels is not naive about the asymmetry. It is adjusting to it.

Stakes and the next twelve months

If the order holds, the immediate winners are the standalone AI companies whose distribution problem on Android is the single biggest bottleneck in their growth. OpenAI and Perplexity, named in the framing of the Commission's case, would gain a structural on-ramp to hundreds of millions of European users. Handset makers with their own assistant ambitions, Samsung's Bixby most visibly, get a second lease on relevance.

The loser, in the narrow sense, is the integration premium Google currently collects on every Android device shipped. In the broader sense, the loser is the assumption that an operating system and a flagship AI product can be co-designed without regulatory friction. That assumption is now gone in Europe. Whether it travels depends on how the next twelve months of compliance negotiations and potential litigation play out, and on whether the order becomes a template that other jurisdictions, with the UK and India the obvious candidates, are willing to copy.

The Commission will publish the formal decision in the EU's official journal in the coming weeks; Google's first compliance window typically runs six months, with the clock starting on the date of notification. Watch that date. It is when the abstract fight becomes a product spec.

How Monexus framed this vs the wire: most coverage of the order treats it as a fine story. The more useful frame is that Brussels is steadily rewriting what it means to be a gatekeeper in a market where the gatekeeper's most valuable product is no longer a search bar but a model, and the device-level prompts that feed it.

Wire provenance

This editorial synthesis draws on the following public wire/social posts:

• https://x.com/pirat_nation/status/2026-07-17T12:00