The European Commission adopted a decision on 16 July 2026 requiring Google to enable effective interoperability between Google Android and third-party AI services, under Article 6(7) of the Digital Markets Act. Google must open 11 specific Android features to rival AI developers, across the whole Android ecosystem, and make them work as well for those developers as they do for Google. The decision is not a finding that Google broke a law. It specifies what compliance has to look like going forward, and the first deadline is Android 18 by 1 August 2027.
What the decision requires
The obligation, as set out on the European Commission's Digital Markets Act developer portal, is that Google provide developers with "free and effective interoperability with hardware and software features controlled by its operating system, Google Android", enable that across the entire Android ecosystem, and ensure the access is "equally effective to those available to Google".
That last clause is the load-bearing one. Access with a worse API, a slower path or a permissions wall would satisfy the letter of interoperability and none of the point. The Commission wrote parity into the requirement instead of leaving it to be litigated later.
This came out of a specification proceeding opened in January 2026, and it is separate from the self-preferencing case about Google favouring its own services in search results. Different article, different question.
The 11 features Google has to open
They fall into four categories.
Invocation
- Long-press home button activation for third-party services
- Always-on hotword detection, so a rival voice assistant can be woken by voice
Context
- Centralized access to apps' on-device data
- Context-aware intelligence, enabling proactive suggestions
- Access to real-time device inputs covering microphone, camera, screen and speakers
Action
- Structured on-device integration with other apps
- Screen automation for completing multi-step tasks
- System integration, including brightness, media and Bluetooth controls
Resource
- System-level on-device AI models, including Gemini Nano
- On-device model implementation capabilities
- Background execution permissions
Read as a set, that is most of what separates a preinstalled assistant from an app. Invocation is how a user reaches it without thinking. Context is what lets it answer without being told everything twice. Action is what turns an answer into a completed task. Resource is what lets it run locally instead of paying for a round trip to a server.
What third parties get out of it
The Commission's stated outcome is that AI assistants can deliver voice activation, cross-app task execution, proactive suggestions, live translation and task automation. Those capabilities were previously reserved for Gemini. A rival assistant on Android today can be excellent and still lose, because the user has to open it, and the assistant already wired into the hardware does not need to be opened.
The timeline is long
| Deadline | Requirement |
|---|---|
| 1 August 2027 | Implementation in Android 18 |
| 1 August 2028 | Concurrent hotword detection in Android 19 |
August 2027 is over a year away, and concurrent hotword detection, which is what lets more than one assistant listen for its wake word at once, is more than two years out. In AI product terms those are long horizons. The assistant market of August 2027 may not have the same shape, the same players or the same interaction model as the one this decision was written for. Remedies with multi-year runways have a habit of arriving to a problem that has already moved.
Why this matters
Assistant distribution on mobile has been an operating-system advantage rather than a product one. The default assistant is the one that answers, and the habit forms around whatever is closest to the hand. Prising open invocation, on-device context and the local models is what would let a rival compete for that habit rather than for a download.
If it works, more of the questions people currently type into a search box get spoken into an assistant that is not Google's. That is a slow reweighting of where discovery happens, and it points the same direction that AI answers have already been pointing: fewer ranked links, more synthesized responses, more places where a brand is either cited or invisible.
What this means for Thai marketers
Nothing changes for Thai users on this timeline. The decision is EU-scoped and the Commission's pages make no claim about Thailand. Google is not required to ship these changes globally, and the decision does not say it will. It might, because maintaining two Androids is expensive, or it might not, because keeping the EU version separate is a well-worn playbook. Both outcomes are live and neither is a prediction worth planning around.
What makes the direction worth a bookmark is Android's share of the Thai smartphone market. If assistant choice does open up on Android generally, it opens up on most phones in Thailand. The practical response is the one already running: assume a growing share of questions get answered by an assistant rather than a results page, and make sure your content is retrievable and citable in that context. That is the work behind generative engine optimisation and AI SEO, and it pays off regardless of which assistant wins the home button, because being cited by AI assistants depends on your content, not on Google's compliance schedule.
FAQ
Is this the same as the EU case about Google favouring its own services?
No. That one is about self-preferencing in search results. This is a specification decision under Article 6(7) of the DMA about interoperability with Android.
Does it mean rival assistants can use Gemini Nano?
Yes. System-level on-device AI models, Gemini Nano among them, are in the list of features Google must make available.
When does any of this ship?
Android 18 by 1 August 2027, with concurrent hotword detection in Android 19 by 1 August 2028.
Will Thai Android phones get these features?
Unknown. The requirement covers the EU. Whether Google extends it elsewhere is Google's decision, and the ruling does not require it.
The short version
The Commission has named 11 Android capabilities and told Google to hand them to competitors on equal terms by August 2027. It is a serious attempt to make assistant choice real rather than nominal, and the deadline is far enough out that the market may rearrange itself first. For Thailand, this is a signal to watch, not a change to respond to.
If you want to know how your brand currently shows up when an AI assistant answers instead of a search results page, our team can take a look.
