EU Forces Google to Open Android AI to Third

EU Forces Google to Open Android AI to Third Parties — Gemini Becomes a Contestant, Not a Default

The European Commission's July 16, 2026 Digital Markets Act decision forces Google to open 11 Android AI features to rival assistants by August 2027 and share anonymized search data with competing engines — the first forced opening of a mobile operating system's AI layer.

The European Commission's July 16, 2026 Digital Markets Act decision forces Google to open 11 Android features to rival AI assistants by August 2027 and to share anonymized search data with competing engines — the first forced opening of a mobile operating system's AI layer. The decision, landing two weeks after the EU Court of Justice upheld a €4.1 billion Android antitrust fine, does something the fine alone could not: it turns Gemini from a default into a contestant on a platform Google built and still controls, and it establishes that AI assistants — not search boxes — are now the gateway regulators intend to keep contestable.

The Decision in Detail

The Commission's specification proceedings, opened on January 27, 2026, under Article 6(7) of the DMA, targeted features Google reserves for its own AI services, principally Gemini. The final decision requires Google to grant third-party AI assistants equally effective access to 11 Android capabilities across five categories: invocation (custom wake words, long-press home-button and navigation-handle triggers, Circle to Search integration), context (centralized access to on-device app data, proactive suggestions, keyboard-level AI inputs), actions (autonomous control of installed apps, OS settings like brightness and Do Not Disturb), system services, and processing resources including on-device machine-learning models, according to the European Commission's DMA portal.

The legal architecture matters. Alphabet was designated a gatekeeper for Google Android on September 5, 2023, triggering Article 6(7), which requires gatekeepers to provide third parties with "free and effective interoperability" with hardware and software features accessed or controlled via their operating system, as the Commission's consultation page lays out. The July 16 decision specifies, feature by feature, what "effective" interoperability means in practice: a general statutory obligation becomes an 11-feature technical mandate with deadlines.

Google must implement the 11-feature interoperability in Android 18 by August 1, 2027 at the latest. Concurrent hotword detection, allowing multiple AI assistants to be triggered simultaneously by voice, is deferred to Android 19 by August 1, 2028. By February 1, 2027, Google must publish draft eligibility terms for consultation; final terms by May 1, 2027; certification applications accepted from that date, with a four-week assessment window. Independent third parties, not Google alone, will certify eligibility. The interoperability solutions must be free, documented, testable, and equally effective to what Google's own services use on all Google Android devices, including those from third-party OEMs, per the binding annex of measures. The annex specifies that Google must make APIs relied upon by Circle to Search available to third parties, ensure interoperability solutions work consistently across Android versions and device form factors, and provide new functionalities to third parties at the same time they reach Google's own services.

The second decision, under Article 6(11), tackles search data. Google must share anonymized ranking, query, click, and view data with eligible third-party search engines on fair, reasonable, and non-discriminatory terms. Critically, AI chatbots offering search functionality are now explicitly eligible beneficiaries, a direct attempt to prevent Google Search's data advantage from extending to Google's AI chatbot layer, according to the Commission's search-data specification page. The data must be shared via a method and with a latency Google uses internally, with latency not less than seven days. Beneficiaries can access data up to five years per engine. The measures exclude invalid traffic from the dataset.

The data comes with guardrails. Beneficiaries cannot use shared data to train general-purpose AI models, for advertising or consumer profiling, or to systematically replicate Google's results. Anonymization follows a multi-layered method developed with internal and external privacy experts and aligned with draft Joint Guidelines on the DMA-GDPR interplay from the Commission and the European Data Protection Board. Beneficiaries must pass an independent audit before receiving data, within six months of starting processing, and annually thereafter. The Commission can order ad hoc audits outside the yearly window if concerns arise.

Two Enforcement Tracks, One Logic

The July 16 DMA measures and the July 2 Court of Justice ruling upholding the €4.1 billion Android fine are separate instruments operating on the same logic. The fine, reduced from the original €4.3 billion in 2018 and trimmed again in 2022, punishes past conduct: Google's requirement that manufacturers pre-install Google Search and Chrome as a condition of accessing the Play Store, payments for exclusive pre-installation, and prohibitions on selling "forked" Android devices, BBC News reported. The Court of Justice dismissed Google's appeal on July 2, 2026, closing an eight-year litigation arc, according to The Economist. A Google spokesperson said the judgment "fails to recognise" the firm's "significant investment to ensure Android remains open, interoperable and free," and noted the company had adapted its agreements after the 2018 decision.

The DMA measures do something different. They are structural and forward-looking. The fine says: pay for what you did. The interoperability order says: open up what you are building. Together they bracket Google's mobile strategy, penalizing the conduct that built the Android search moat while preemptively dismantling the AI moat under construction.

The Commission's preliminary findings, sent to Google on April 27, 2026, framed the stakes explicitly. "The smart mobile device market is at a technological inflection point, with AI services becoming central access points on mobile devices," the Commission's case summary states. With roughly 60% of EU mobile users on Android, the Commission reasons, the OS is the gateway through which standalone AI services reach users — and the gateway cannot remain under a single company's control. The case summary notes that Alphabet is "uniquely placed to leverage its strength" in AI through access to infrastructure (Google Cloud), foundational models (Gemini), platform integration (Gmail, Maps, YouTube), and distribution via Android.

The transatlantic parallel is striking. On September 2, 2025, US District Judge Amit Mehta ruled that Google must end exclusive distribution contracts and share portions of its search index and click-and-query data with competitors but declined to order Chrome or Android divestiture, NPR reported. Judge Mehta explicitly acknowledged that AI's rise "changed the course of this case," barring exclusive deals for Gemini as well as Search, but stopped short of mandating AI-layer interoperability on Android. The EU has now gone where the US court did not: forcing open not just distribution contracts but the operating system's AI plumbing itself. The DOJ had sought divestiture of Chrome and oversight of Android; the judge called a Chrome selloff "a poor fit," per BBC News. The EU did not need a court trial to reach a structural remedy — the DMA's ex-ante framework delivered one through regulatory specification.

The Microsoft Precedent, Recast

The structural logic mirrors the Commission's 2004 Microsoft decision, which fined the company €497 million and ordered it to disclose interoperability information for work group server protocols — the "complete and accurate specifications" competitors needed to build Windows-compatible server software, as recorded in the EUR-Lex decision text. The Court of First Instance upheld that remedy in 2007, finding that Microsoft's refusal to supply interoperability information limited technical development "to the detriment of consumers," per the CFI judgment. The 2004 case originated from a December 1998 complaint by Sun Microsystems, which alleged Microsoft withheld interface information needed for work group server operating systems to interoperate with Windows, as the Commission's case documents show.

But the Google decision operates on a different scale. Microsoft was ordered to disclose protocol specifications — documentation. Google is ordered to build and maintain live interoperability frameworks across an ecosystem running on hundreds of OEM device variants, with new functionalities made available to third parties at the same time they reach Google's own services. The DMA's ex-ante architecture means Google must keep the door open by design, not retroactively, and face penalties of 4% to 20% of global annual turnover for non-compliance, according to CSIS analysis. The CSIS report notes that seven gatekeepers — Meta, Alphabet, Amazon, ByteDance, Apple, Booking, and Microsoft — have been designated across 23 core platform services.

That enforcement teeth is not theoretical. In December 2025, the Commission imposed interim measures on Meta, ordering it to restore third-party AI assistant access to the WhatsApp Business API within five working days while an antitrust investigation proceeds — a move Meta called "regulatory overreach" and pledged to appeal, as BBC News reported. The Commission's competition chief, Teresa Ribera, framed it bluntly: "In rapidly evolving markets, competition can be lost long before a final decision is adopted." The Meta case demonstrates the Commission's willingness to act at AI's speed rather than litigation's speed.

Who Benefits, Who Loses

The immediate winners are AI providers with the engineering capacity to build deep Android integrations: OpenAI, Anthropic, Mistral, and Meta. Samsung, which ships its own Galaxy AI on Android devices, gains leverage to differentiate without depending solely on Google's stack — a shift that could reshape OEM-Google negotiations across the Android ecosystem. European privacy-focused search engines — Ecosia, Qwant — gain access to the anonymized search data they have long argued was essential to competing, as Agence Europe reported. The Agence Europe bulletin notes that the measures require access to Google apps like Gmail, Calendar, Maps, and YouTube under non-discriminatory terms.

The longer-term beneficiary is the Commission's regulatory model itself. If the Android AI interoperability remedy holds and produces genuinely competitive AI assistants on European devices, it becomes the template for every gatekeeper designation that touches AI: Apple's iOS, Meta's WhatsApp, Amazon's Alexa ecosystem. The Ars Technica analysis frames this as the first test of whether ex-ante structural regulation can keep pace with AI product cycles that move faster than any market the DMA was originally designed for.

The losers are not just Google. The Commission's own preliminary findings note that Alphabet has argued the DMA has "materially degraded user experiences," citing a 50% increase in searches users complete to reach destinations and 30% traffic losses for businesses, per CSIS. That claim comes from Google's Head of Competition, Oliver Bethell. The CSIS analysis also notes that translating principles like interoperability into technical standards has resulted in product feature delays as firms square compliance demands with performance and security priorities.

Google's response, so far, has been measured. The company adapted its Android agreements after the 2018 Commission decision and has framed its compliance posture as ongoing, a spokesperson told BBC News. Google has not indicated whether it will challenge the July 16 specification measures. The company faces separate DMA scrutiny over self-preferencing in Google Search and anti-steering in Google Play, with the Commission releasing preliminary findings on both in March 2025, according to CSIS. Fines in those cases are expected.

The risk for European users is feature degradation — the same complaint Google raises. If interoperability layers introduce latency or complexity, and if Google opts to limit advanced Gemini features in the EU to maintain parity obligations, European Android users could receive a diminished experience. The Commission's decision attempts to preempt this by requiring that interoperability solutions be "equally effective" and that Google not reserve access points through technical or contractual means. Whether that language is enforceable in practice is the open question. The Brookings Institution analysis of earlier DMA gatekeeper compliance — focused on Apple's app store changes — found that gatekeepers can create "huge disincentives" for competitors through seemingly compliant but practically onerous requirements. The same risk applies here: Google could publish eligibility terms, provide documentation, and offer APIs that technically satisfy the decision while practically discouraging third-party adoption.

Diplomat View

The EU's July 16 decision is the most consequential structural intervention in a mobile operating system since the 2004 Microsoft remedies — and arguably more ambitious, because it targets a live AI layer still under construction rather than a mature server market. The contest that matters is not search but the AI gateway, and the Commission has moved to keep it open before Google can lock it.

The €4.1 billion fine punishes history. The interoperability order engineers the future. If Google implements the 11 features as specified and third-party assistants genuinely achieve parity on Android 18, the decision reframes the DMA as a tool capable of governing AI competition in real time — not just policing search defaults after the fact. If Google delays, litigates, or delivers interoperability that is technically compliant but practically inferior, the Commission's enforcement capacity faces its hardest test.

What would change the forecast: a successful Google appeal challenging the specification measures' scope, an Android 18 release that ships interoperability APIs with gating requirements that third parties cannot practically meet, or a US-EU regulatory divergence sharp enough that Google offers materially different Android experiences on either side of the Atlantic. Short of those, the decision stands as the first structural opening of a platform's AI layer by regulatory force.

What to watch next:

• February 1, 2027: Google must publish draft eligibility terms for third-party AI assistant certification, open to Commission and third-party consultation.
• August 1, 2027: Android 18 release deadline — the first test of whether the 11 interoperability features ship as specified.
• August 1, 2028: Android 19 deadline for concurrent hotword detection — the moment multiple assistants can be voice-triggered simultaneously on a single device.

The bottom line: the EU's July 16 decision does not fine Google for past conduct — it rewrites the rules of how AI assistants compete on the world's largest mobile operating system. If the 11-feature interoperability mandate holds through Android 18, Gemini loses its home-field advantage on 60% of European mobile devices, and the DMA becomes the first regulatory tool to structurally open a platform's AI layer before the market locks in.