The European Commission published two sets of binding specification measures against Google under the Digital Markets Act on 16 July, and together they read as the most concrete attempt yet to legislate open competition into how AI assistants reach a phone's operating system, according to the Commission's own guidance document. The first measure requires Google to give competing AI assistants equal access to Android functionality currently reserved for Gemini: voice activation on par with "Hey Google," the ability to take actions inside other apps on a user's behalf, and access to contextual signals like a recently visited place. The second requires Google to share anonymised search query, click and ranking data with rival search engines and AI chatbot providers, data that only Google Search collects at the scale needed to make a competing product genuinely useful. CNBC reported that Google has already objected publicly, with global affairs president Kent Walker arguing the changes risk weakening privacy and security safeguards for European users.
The two dates that actually matter
Search data sharing is due to begin in January 2027; Android AI interoperability has a longer runway, due by July 2027, per Tech Times' coverage of the ruling. Non-compliance carries penalties of up to 10% of Google's annual worldwide revenue, which is the kind of number that tends to concentrate a vendor's engineering priorities regardless of how strongly it objects in a press statement. This follows a separate July court ruling that closed off one of Google's remaining legal avenues to delay the interoperability requirements, so the eighteen-month runway enterprises now have is a genuine planning window, not a deadline likely to move again.
Why this matters even if you're not choosing between Gemini and a rival assistant
The direct effect is obvious for any enterprise building or evaluating an AI assistant product that needs to integrate with Android: the access model you're designing around today is legally required to change materially within eighteen months, and building tightly around Gemini-specific integration points that a rival wouldn't get is a decision worth revisiting now rather than after July 2027 forces a rebuild. The less obvious effect is the search data question. Anonymised query, click and ranking data at Google's scale has been, in practical terms, the biggest single advantage a search or AI answer product could have, and enterprises with a stake in search-adjacent products, retrieval-augmented generation pipelines drawing on live web data, or competitive intelligence tooling should expect the market to shift meaningfully once rivals can build on data they've never had access to before. We've written before about vendor due diligence as an ongoing discipline rather than a one-off procurement gate; a ruling that reshapes a major platform vendor's obligations eighteen months out is exactly the kind of event that belongs on a due-diligence calendar, not just a news feed.
There's a governance angle too. Enterprises that have leaned on Android's tight integration between OS-level functionality and a single assistant, for good reasons, including simpler data flows and a narrower vendor security surface, will need to reassess that surface once multiple assistants have comparable access. Our piece on data residency and sovereign cloud covers a related pattern: regulatory intervention that changes where and how data moves rarely stays contained to the specific dispute that triggered it, and mobile AI vendor risk assessments written before 16 July should be revisited with this ruling in mind rather than assumed to still hold.
What to actually do about an eighteen-month runway
The temptation with a deadline this far out is to file it under "watch this space" and move on. That's a reasonable instinct for most regulatory developments, but this one changes an assumption, exclusive platform-level integration for a single AI assistant, that a fair number of enterprise mobile strategies were quietly built on. The organisations that will handle the July 2027 deadline calmly are the ones treating the next twelve months as a review window, not the ones starting the review in June 2027.
- Flag both deadlines, January 2027 for search data sharing and July 2027 for Android AI interoperability, on any AI or mobile platform roadmap that currently assumes single-assistant integration.
- Review whether your organisation's Android-integrated AI features depend on access Google currently reserves for Gemini, and assess what changes once rival assistants have equivalent access.
- Reassess vendor risk for any product strategy built on Google Search's current data advantage, since that advantage is legally required to narrow from January 2027.
- Revisit data governance assumptions for mobile AI integrations that predate this ruling; a changed access model can change your own data flow and security surface even if you never touch Gemini directly.
- Treat this as a live compliance question rather than a settled one; Google has already signalled it will contest aspects of the ruling, and enterprises should track how the specification measures evolve rather than planning against today's text as final.
Regulatory stories about Big Tech platforms tend to get filed as background noise until a deadline arrives without warning. This one comes with two dates attached and a runway most organisations don't get. If you'd like help assessing what this ruling changes for your mobile AI strategy or vendor risk posture, email sales@halfteck.com.