What the EU’s DMA Order Actually Does to Android
The EU Android AI assistants decision is a binding order under the Digital Markets Act that forces Google to grant rival AI assistants equal access to 11 core Android features, including microphone, camera, and on‑screen content, and to share anonymized Google Search data with competing search and AI services by August 2027, with the explicit goal of weakening Google’s dominance over mobile AI and search. This is not a fine or a warning; it is a blueprint for how Android itself must change. Under the Digital Markets Act Google is treated as a gatekeeper, and the European Commission has now told that gatekeeper what it must build. One binding specification decision compels Google to give rival AI assistants the same reach into Android that Gemini enjoys: wake‑word activation with the screen off, ambient sensor access, and the ability to control other apps in the background by imitating taps and typing. The second forces Google to hand anonymized Search query, click, and ranking data to rival search engines and AI chatbots that perform search, for a cost‑based fee. Taken together, these measures aim to break Google’s effective monopoly over mobile AI and search capabilities.
From Locked-In Google Assistant to Real Rival AI Access on Android
Until now, rival AI access on Android has been cosmetic: third‑party assistants could live in apps, but they could not match the deep integration of Google Assistant or Gemini. Competing assistants were limited in their access to key functionalities, which made them less attractive to the roughly 60% of mobile users who rely on Android in the EU. The DMA decision directly attacks that structural disadvantage. The ruling covers 11 operating system features, splitting them into five restricted and six unrestricted capabilities. Ambient data—microphone input, system audio, camera, screen contents, location, and motion sensors—must be opened to all third‑party apps, including user‑installed AI assistants, under the same lighter consent prompts Google’s own services use. Paragraph 119 explicitly bars Google from limiting which apps may call these features or what use case they serve. In other words, Google can still enforce process isolation and encryption for safety, but it can no longer decide that only its own assistant deserves always‑on hotword detection or continuous sensor feeds.
How Users’ AI Experience Changes by Android 18 and Beyond
The practical impact for ordinary users is substantial: by Android 18, and no later than 1 August 2027, you should be able to pick a preferred AI assistant and have it behave like a first‑class citizen on your phone. The Commission’s decision guarantees that users can activate their chosen assistant via voice commands, similar to the familiar “Hey Google” wake word, and have it perform actions inside apps on their behalf. By August 2027, a certified assistant—or an uncertified one that the user has explicitly waved through—will be able to open apps on a virtual display, read their screens, and click through them in the background while the user does something else. This is a qualitatively different Android: instead of one default brain, multiple assistants can compete to be the interface you use for messaging, navigation, calendar management, and media control. Multi‑assistant hotword detection, where several assistants can listen in parallel, is scheduled for Android 19 and 1 August 2028, pushing the platform toward an ecosystem where users can mix and match AI tools as easily as they install apps today.
Search Data Sharing: Cracking Open Google’s Crown Jewel
The most radical part of this Digital Markets Act Google ruling isn’t on the phone’s sensors but in the cloud: the obligation to share anonymized Search data. The second specification decision forces Google to provide anonymized query, click, and ranking data to rival search engines and AI chatbots that perform search, priced on a cost‑based fee structure. By doing so, regulators are attacking the data advantage that underpins Google’s dominance; anonymized logs of what people search, what they click, and how results rank are the raw material from which better search and AI models are trained. The anonymization method runs in three passes, stripping direct identifiers and attributes that allow records to be stitched back together, such as usernames, IP addresses, precise timestamps, and input formats. Supporters argue this gives alternative services “a fighting chance” to innovate in search and conversational AI without recreating Google’s data hoard from scratch. Google, however, warns that forcing such sharing and deep system‑level permissions could trigger what it calls a privacy and security catastrophe for millions of users, setting up a clash between competition policy and platform risk management.
Security Fears vs. User Choice: Who Wins by 2027?
The Commission’s Android programme tries to balance EU Android AI assistants competition with security by introducing a Qualified AI Assistant Programme for the five restricted features. Google must allow third‑party Trusted Certification Authorities to certify assistants into this programme free of charge, accept those certifications without extra conditions, and avoid revoking them arbitrarily. Certification can only check for a narrow set of safeguards: reconfirming user intent before sensitive actions, minimizing unintended data disclosure, meeting baseline mobile app security, and resisting agentic risks that would negate user intent. Anything beyond that requires the Commission’s approval—and the same bar applies to Google’s own Gemini. Users also gain a powerful override: paragraph 135 obliges Google to let people consent their way out of the certification requirement per service, per device, without hiding the switch behind developer‑only settings. As this regulatory chess match continues, Android users may find themselves choosing not just between assistants, but between the EU’s vision of an open, multi‑assistant ecosystem and Google’s warnings about weakened hardware guardrails and potential security disasters. My view is blunt: if Google wants to be the default brain of half the smartphones in Europe, it must prove it can compete on merit, not on locked doors and privileged sensor access.
