Android Interoperability: EU DMA Ruling Forces Google to Open Wake Word and AI Features

The European Commission (EC) has adopted a decision under the Digital Markets Act (DMA) requiring Alphabet (Google) to open eleven Android system features to third-party assistants on equal terms. This ruling targets "gatekeeper platforms" to ensure digital markets remain competitive, specifically removing Google's exclusive access to low-power hardware and system-level integrations that previously gave Gemini and Google Assistant an unfair advantage over third-party alternatives like Home Assistant.

Mandatory Opening of Eleven Android Features

The EC ruling requires Google to provide third-party developers with interoperability that is "equally effective" to its own services, free of charge. The mandate covers eleven specific areas, with several critical technical capabilities now open to competition:

Low-Power Wake Word Detection

Google must allow third parties to implement wake word detection using the device's Digital Signal Processor (DSP). Previously, third-party apps were forced to run detection on the CPU, leading to significant battery drain (increasing from ~1% to ~15% in some cases) and permanent microphone privacy indicators. The new requirements include:

  • DSP Integration: The ability to run first-stage detection on the DSP to minimize power consumption.
  • Second-Stage Validation: The ability to run a second-stage validation on the CPU after the DSP identifies a potential wake word.
  • Decoupling from Default Role: Access to these features must not be contingent on the app being the system's default assistant.
  • Concurrent Detection: Multiple services (both Google's and third-party) must be able to run wake word detection concurrently.

AI and System Integration

Beyond voice triggers, the ruling opens several high-level AI and automation capabilities:

  • On-Device AI Models: Third-party AI services must have equal access to on-device models (ODMs), including Gemini Nano, with guaranteed performance parity.
  • Structured App Integration: AI services can now interact with Google apps (Gmail, Calendar, Drive, Docs, Maps, YouTube, Messages, and Phone) to perform tasks like sending messages or scheduling meetings via OS-level integration channels.
  • Screen Automation: Third-party assistants can automate multi-step tasks within apps by imitating user behavior in a separate virtual window, allowing background task completion.
  • System Controls: Access to ambient data (microphone/camera) and system-level controls under the same conditions as Google's own services.

Implementation Timeline and Compliance

Google is legally bound to a strict rollout schedule for these interoperability features:

Feature Deadline Android Version
General Interoperability Features August 1, 2027 Android 18
Concurrent Hotword Detection August 1, 2028 Android 19

To prevent "malicious compliance," the EC requires Google to deliver solutions that match Google's own services in terms of ease of use, speed, and energy consumption. Google must provide complete documentation, testing tools, and report progress to the Commission on a monthly basis.

Technical Impact on Home Assistant

For the Home Assistant community, this ruling removes several technical barriers to creating a local-first voice assistant experience:

  • Battery Efficiency: Moving first-stage detection from the CPU to the DSP will significantly reduce the power overhead of always-on listening.
  • Privacy via Sandboxing: The ruling requires wake word confirmation to run in a secure, isolated process (sandboxing) via the DSP. This ensures audio cannot be sent anywhere until the wake word is confirmed, moving from a trust-based model to an OS-enforced privacy model.
  • Multi-Assistant Coexistence: Users will no longer have to choose between Gemini and a third-party assistant. They can maintain Gemini as the default for general tasks while using a custom wake word (e.g., "Okay Nabu") for home automation.

Industry Perspectives and Counterpoints

Google has contested the ruling, arguing that granting third parties "sensitive and powerful device permissions" exposes user data without proper consent. However, advocates for the ruling argue that these capabilities already exist and are used by Google without explicit user approval for every instance.

Community discussion highlights several remaining concerns:

"The core issue is not 'Google not allowing a feature', it's that small businesses cannot buy phones, install a patched version of Android without a restriction and sell them to make money."

Other developers have noted the technical challenge of implementing concurrent wake words on DSPs designed for a single trigger, suggesting that this may increase the frequency of CPU wake-ups and potentially impact the very battery efficiency the ruling seeks to protect.

Summary of Key Requirements

  • Equal Access: Third-party assistants must have the same hardware and software access as Google's own services.
  • No Default Requirement: Features cannot be locked behind the "default assistant" role.
  • No Cost: Interoperability must be provided free of charge.
  • Verification: Google must report monthly to the EC and provide public consultation on eligibility terms by February 2027.

Sources