That exists today it’s called the Bluetooth standard.No one is asking for keys to the kingdom. Just adequate APIs for interoperability.
That exists today it’s called the Bluetooth standard.No one is asking for keys to the kingdom. Just adequate APIs for interoperability.
Android is open. If iOS is really limiting Bose’s ability to compete, then Bose can build an amazing experience on Android that isn’t possible on iOS and point to Apple’s rules as to why it doesn’t work on iOS. But Bose shouldn’t be given access to Apple’s translation tech for free.This is not about the competition between Apple and Google. It's about companies that want to compete with Apple AND Google in the audio accessory or the translation app market. It would be terrible if only Apple and Google could build high-end headphones or translation apps because of anti-competitive technical barriers.
Why do you think this is the only possible outcome? The Bluetooth SIG exists for exactly this purpose, to advance the technology for the benefit of the whole industry. In fact just this year Apple decided to increase their involvement in Bluetooth standardization significantly by becoming a voting member, most likely in anticipation of more regulatory pressure.
I agree that not all market regulation is harmful to innovation. For example, as much as I disagree with the DMA’s third-party App Store requirement, I don’t think it significantly harms innovation. But the “immediately give access to any software feature to your competitors, for free” part of the DMA definitely harms it.I also don't agree with the premise that market regulation is harmful to innovation. It only applies to companies that have already become a huge player in their respective markets, and that is a really nice problem to have.
What are you talking about here? Apple supports AAC over LC3. Neither are proprietary.This statement is most certainly not true. Apple uses a lot of proprietary tech on top of Bluetooth to make interactive (duplex) voice applications work with AirPods. Third party wireless headphones don't have access to these Bluetooth extensions and therefore can't really compete with Apple in this space. If you have ever tried the Hands Free Profile with third-party wireless headphones, you know what I'm talking about.
The Bluetooth group has introduced a new standard for the transmission of audio in 2020 to address most shortcomings of the old audio profiles called Bluetooth LE Audio (v5.2). For very strange reasons, Apple hasn't implemented this feature on iOS yet though. Could it be because they want to protect their AirPods market share?
The right thing for Apple to do would be to either allow competitors access to their proprietary Bluetooth extensions, or finally introduce Bluetooth LE Audio. The latter would probably be better for the consumers, because manufacturers would not have to deal with two different standards that are essentially doing the same thing.
Edit: Android has support for modern Bluetooth Audio since Android 13.
This is a very comprehensive article about the current state of Bluetooth Audio (LE) on iDevices:What are you talking about here? Apple supports AAC over LC3. Neither are proprietary.
Within a year or two, LE Audio will be a part of nearly all popular wireless chipsets and their software stacks, and commonplace among at least premium Android devices and many new cars. Without it, Apple risks being left behind, and while it might find its own proprietary way to include similar features in future AirPods, it would be a terrible idea for iPhones to be stuck using Bluetooth Classic when connected to any non-Apple device.
Check the article I posted above about Bluetooth LE Audio. It's Apple who is dragging their feet by not implementing it in iOS. Is this how dominant tech companies should behave to keep competitors at a distance? I'm sure you know the "embrace, extend, and extinguish" strategy Microsoft has become known for. What Apple is doing in the audio accessory space is very similar in my opinion.Apple’s Bluetooth improvements led to better wireless audio for the entire industry, but only because they got to benefit from their investment first. Under the DMA’s logic, those improvements would have AT BEST been delayed by YEARS and most likely would have never been developed because the incentive structure would be completely broken.
I don't think anyone is asking Apple to give other companies access to the translation feature. Any interested competitor would have to come up with their own way to do the on-device audio processing and actual translation. Unless of course Apple decides to provide API access to third-party apps.Android is open. If iOS is really limiting Bose’s ability to compete, then Bose can build an amazing experience on Android that isn’t possible on iOS and point to Apple’s rules as to why it doesn’t work on iOS. But Bose shouldn’t be given access to Apple’s translation tech for free.
So three years later Apple is not only “not behind” but flourishing as well. So much for those prognostications.This is a very comprehensive article about the current state of Bluetooth Audio (LE) on iDevices:
![]()
How Bluetooth LE Audio could amp up the next generation of AirPods
Bluetooth audio is about to level up with LE Audio and the LC3 codec. We can only hope these technologies are coming to AirPods and iPhones soon.www.macworld.com
The article was written in 2022, and iOS still does not support the superior Bluetooth LE Audio modes.
The DMA literally requires Apple to give access to any “hardware or software” feature iOS uses. That’s the almost certainly why Apple isn’t releasing it the EU.I don't think anyone is asking Apple to give other companies access to the translation feature. Any interested competitor would have to come up with their own way to do the on-device audio processing and actual translation. Unless of course Apple decides to provide API access to third-party apps.
That article doesn't address my point. The only part of the spec that Apple doesn't currently support is the LC3 codec, because Apple prefers AAC. Which is not proprietary.This is a very comprehensive article about the current state of Bluetooth Audio (LE) on iDevices:
![]()
How Bluetooth LE Audio could amp up the next generation of AirPods
Bluetooth audio is about to level up with LE Audio and the LC3 codec. We can only hope these technologies are coming to AirPods and iPhones soon.www.macworld.com
The article was written in 2022, and iOS still does not support the superior Bluetooth LE Audio modes.
I think you did not understand the article I linked to. Bluetooth LE Audio (released in 2020) is a new spec that supersedes the old Bluetooth Audio Profiles. It's much more sophisticated and allows many use cases that were not possible with legacy Bluetooth. LC3 is just one very tiny part of the new spec.That article doesn't address my point. The only part of the spec that Apple doesn't currently support is the LC3 codec, because Apple prefers AAC. Which is not proprietary.
This is a lot of legalese and IANAL. My interpretation of the above would be, that Apple has to give access to the APIs used by the translation app, but not the translation service itself.The gatekeeper shall allow providers of services and providers of hardware, free of charge, effective interoperability with, and access for the purposes of interoperability to, the same hardware and software features accessed or controlled via the operating system or virtual assistant listed in the designation decision pursuant to Article 3(9) as are available to services or hardware provided by the gatekeeper.
Repeating what Bluetooth LE Audio is for the third time doesn't contradict what I said. LC3 is the audio codec used with Bluetooth LE Audio. Apple chose to continue to support AAC instead of supporting LC3.I think you did not understand the article I linked to. Bluetooth LE Audio (released in 2020) is a new spec that supersedes the old Bluetooth Audio Profiles. It's much more sophisticated and allows many use cases that were not possible with legacy Bluetooth. LC3 is just one very tiny part of the new spec.
The codec choice is not really relevant here. LC3 is the new baseline codec for Bluetooth LE Audio. It's a replacement for SBC and Apple will most likely support it for compatibility reasons. Apple can still prefer AAC over BLE Audio, if they chose so.Repeating what Bluetooth LE Audio is for the third time doesn't contradict what I said. LC3 is the audio codec used with Bluetooth LE Audio. Apple chose to continue to support AAC instead of supporting LC3.
From your article: "LE Audio requires a new low complexity codec, LC3." Again, Apple is choosing AAC over LC3 (and therefore LE Audio.) My point was simply that the choice Apple is making isn't proprietary vs non-proprietary. It's between two non-proprietary codecs. Most likely do to quality and hardware decoding efficiency if I were to guess.The codec choice is not really relevant here. LC3 is the new baseline codec for Bluetooth LE Audio. It's a replacement for SBC and Apple will most likely support it for compatibility reasons. Apple can still prefer AAC over BLE Audio, if they chose so.
How does Apple’s dominance (far less than half the market, but still) in cellular phones hamper competition in “headphones” in general? The number of products in the EU that make use of wireless headphones are ENORMOUS, far dwarfing the Apple based use case of “1 family of phones”.Differentiation is not an issue per se. It becomes problematic, when a company uses its dominance in one area to seriously hamper competition in a related market like headphones.
I am also not a lawyer, and definitely not a European one, but "access to the same software features" sounds to me like API access to that feature. Not "APIs so Bose can build a similar feature." (Particularly given those features ALREADY exist in third-party apps). Especially when you consider some of the requirements the EU has already placed on Apple under the DMA (notifications on third-party smart watches, easy bluetooth pairing for headphones and other devices, etc.). The EU specifically requires that "all features on Apple will have to enable interoperability for any type of connected device, free of charge, via complete, accurate and well-documented frameworks and APIs."This is a lot of legalese and IANAL. My interpretation of the above would be, that Apple has to give access to the APIs used by the translation app, but not the translation service itself.
Of course it's fair competition. Apple built both devices and the OS. They did the hard work to create that integrated platform. Yes, Apple controls iOS, but they earned that position by investing billions in R&D to build something users actually want.If a third party would like to offer a live translation service, it should have access to the same (or equivalent) operating system API as Apple's solution. This is deemed necessary, because otherwise third-party services would be at a disadvantage from the get-go, which would not be fair competition.
I really don't think this has anything to do with what we're actually arguing about, but I'll just say again that if the DMA were in place prior to AirPods being released, the Bluetooth LE Audio standard wouldn't exist. (I also suspect AirPods wouldn't be available in the EU either, or would have come way later.) The Bluetooth LE Audio standard came years after Apple had already solved these problems with their proprietary work with AirPods. And Apple contributed that knowledge to the standard! This is exactly how innovation should work: Apple invested in solving hard technical problems first, benefited from their innovations, and then contributed to industry standards that everyone could use.We agreed, that Apple uses some proprietary protocols to communicate with AirPods to enable real-time audio communication. This is necessary, because the old Classic Bluetooth Profiles have audio quality and latency issues.
Now to comply with the DMA, Apple could allow third parties to use the proprietary Bluetooth extensions, or preferably, implement Bluetooth Audio LE, which is the industry standard that provides most of the advantages of Apple's proprietary Bluetooth tech.
If all the translation isn’t done on device, and or some amount of audio is uploaded to the cloud or used to refine the analysis of the users voicePRINT etc., that would be a GDPR no no.
I don't have time to answer all your points, sorry. We are also going around in circles a bit in this discussion.So when Apple's lawyers looked at the translation feature, I suspect they reasonably concluded the DMA would require them to provide the same level of access to competitors that Apple's own apps get: meaning access to the translation service, not just telling competitors to build their own.
I had the opportunity to test it out on my AirPods Pro 2. It was actually pretty great. Th delay is about 3 seconds, but you can read the translation on the iPhone and it’s almost instant. It works pretty well to be honest.Chances are it won't be a huge miss for the customers since we have no idea if the feature works at all as it was demonstrated.
Agree we're going in circles. A shame the EU is keeping this feature away from its citizens because either it doesn't believe in intellectual property or have any idea how business works.I don't have time to answer all your points, sorry. We are also going around in circles a bit in this discussion.
I'll just add this. After looking at the details how "Live Translation" is implemented in iOS 26, it's a little bit clearer to me what the holdup is about. Confusingly Live Translation seems to be an umbrella term for several integrations across many first-party apps. You can not only use it for translating live speech using AirPods, but also inside the Messages and FaceTime apps. This of course makes integrating third-party translation service more complicated and requires more effort than I originally thought.
Live Translation is really a good feature and in my opinion has the potential to be much more popular than mirroring. My bet would be that it's in Apple's own interest to comply with the law to everyone's satisfaction as quickly as possible 🤞.
Saw the demonstration bu Justine and yeah, it was surprisingly good.I had the opportunity to test it out on my AirPods Pro 2. It was actually pretty great. Th delay is about 3 seconds, but you can read the translation on the iPhone and it’s almost instant. It works pretty well to be honest.
There’s already apps out there. There’s even one where you share your AirPod with someone else so both get the audio translation.In short, EU iPhone users will never get the Live Translation feature. That is unless some third party writes their own app and gets it on the iOS App Store.
I'm looking at the big picture and am quite happy with the way our political system and economy is managed at the EU level. There are really more important issues than fretting about the lack of certain features on my smartphone.Agree we're going in circles. A shame the EU is keeping this feature away from its citizens because either it doesn't believe in intellectual property or have any idea how business works.
I'm looking at the big picture and am quite happy with the way our political system and economy is managed at the EU level. There are really more important issues than fretting about the lack of certain features on my smartphone.
If you're happier with a laissez-faire type of market economy, and think that this leads to the best outcomes for you and your family, then I have nothing against that. You're definitely living in the right country then, as far as I can tell.