{"id":49954,"date":"2025-11-06T15:44:44","date_gmt":"2025-11-06T20:44:44","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=49954"},"modified":"2025-11-26T15:11:43","modified_gmt":"2025-11-26T20:11:43","slug":"airpods-live-translation-expands-to-the-eu","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2025\/11\/06\/airpods-live-translation-expands-to-the-eu\/","title":{"rendered":"AirPods Live Translation Expands to the EU"},"content":{"rendered":"

Apple<\/a> (9to5Mac<\/a>, MacRumors<\/a>, Reddit<\/a>):<\/p>\n

\n

Next month, Live Translation on AirPods will expand to the EU, making face-to-face conversations easier by helping users communicate even if they don’t speak the same language.<\/p>\n

[…]<\/p>\n

Live Translation on AirPods is available in English, French, German, Portuguese, Spanish, Italian, Chinese (Simplified and Traditional Mandarin), Japanese, and Korean when using AirPods Pro 3, AirPods Pro 2, or AirPods 4 with ANC paired with an Apple Intelligence-enabled iPhone running the latest software. Live Translation on AirPods was delayed for users in the EU due to the additional engineering work needed to comply with the requirements of the Digital Markets Act.<\/p>\n<\/blockquote>\n\n

So what happened here? What was this extra engineering work? Back in September, Apple said:<\/p>\n

For example, we designed Live Translation so that our users’ conversations stay private — they’re processed on device and are never accessible to Apple — and our teams are doing additional engineering work to make sure they won’t be exposed to other companies or developers either.<\/p><\/blockquote>\n\n

But it doesn’t sound like Apple has opened up Live Translation to third-party Bluetooth devices or to third-party apps. Does the DMA not require that? Or is Apple actually doing that but deliberately left it out of the announcement?<\/p>\n\n

The other main theory for the delay was that Apple had not yet shown the regulators how the feature complied with the GDPR. But would that require “additional engineering work”? Apple was cagey before but now specifically blames the DMA, not the GDPR.<\/p>\n\n

Based only on a plain reading of the public statements above, the logical conclusion is that the initial version of Live Translation had privacy flaws, which the EU forced Apple to address before shipping in that region. That would be a very interesting story and completely at odds with Apple’s framing that the EU’s demands would reduce<\/em> privacy.<\/p>\n\n

There are some other possibilities. Maybe the feature just wasn’t ready before. Maybe Apple created a false conflict to drum up anti-DMA sentiment. Maybe the EU caved and let Apple ship the feature without changes—though that doesn’t explain the additional engineering. All of Apple’s communication about this feature in the EU seems designed to obscure rather than elucidate, so who knows?<\/p>\n\n

Nick Heer<\/a>:<\/p>\n

\n

If Apple wants to be petty and weird about the DMA in its European press releases, I guess that is its prerogative, though I will note it is less snippy about other regulatory hurdles<\/a>. Still, I cannot imagine a delay of what will amount to three-ish months<\/a> will be particularly memorable for many users by this time next year.<\/p>\n<\/blockquote>\n\n

Previously:<\/p>\n