What the EU actually ordered
The European Commission told Google it has to grant rival AI assistants access to 11 Android features. Six of them, including the microphone, the camera, screen contents, always-on hotword detection, system-level on-device models, and background execution, come with no certification barrier at all. Five more, like centralized app data access and Magic Cue-style context awareness, require going through a new Qualified AI Assistant Programme. Google also has to share anonymized Search query, click, and ranking data with competing search engines and chatbots. (The Hacker News)
The timeline is slower than the headline
This is a Digital Markets Act order, not a switch that flips this month. Draft programme terms are due February 1, 2027. Applications open May 1, 2027. Full implementation lands with Android 18 on August 1, 2027, and concurrent hotword detection, meaning more than one assistant listening for its wake word at once, doesn't arrive until August 1, 2028. If you're picturing a rival assistant reading your texts next month, that's not what this is. (The Hacker News)
Google's pushback isn't crazy
Google President Kent Walker argued the order "threatens device security by granting external apps sensitive and powerful device permissions," and pointed to real precedent, including a notification-based prompt injection attack researchers demonstrated against Gemini. The Commission's response is a set of safeguards: user consent requirements, encryption standards, and independent audits of whoever ends up receiving the data. Whether that's enough is genuinely an open question, not a settled one. (The Hacker News)
Why this matters even if you're on an iPhone
Apple's closed model looks a lot more defensible after a week like this one. Nobody is forcing Apple to let a third-party assistant listen through the iPhone's mic by regulatory mandate, at least not yet. But the EU has shown it's willing to force exactly that kind of opening on the platform that resists it least. That's worth watching, because regulators rarely stop at one company once they've built the legal muscle to do it again.
Not advice, just a plain read of what the order says and when it actually takes effect. See also what it takes for a phone to even run on-device AI in the first place. You can see what this studio builds at jcmobileappstudio.com/apps.
Comments
Be kind and stay on topic. Comments are reviewed before they appear.