Granted, Apple generally doesn't do that last part unless forced. I think some kind of timeline on the DMA requirements would be more reasonable. e.g. you have two years to make a feature publicly accessible before fines start accruing.
For a hobbyist? Sure! For a company with half the smartphone market and a trillion dollar market cap? EU doesn't mandate that they define a new standard and support it indefinitely.
Apple is not required to develop or maintain any feature against their will. The DMA is not written like that, it is much more objective and industry-agnostic.
The EU demands that features implemented in the OS to be used by Apple accessories must be made equally available to competing accessory vendors.
Certifying devices to make sure they're safe for users, like "this cable is certified as compatible, it won't set your iphone on fire", seems fine.
Requiring your app to be "certified by apple to sell ebooks", and then only granting that certificate to Apple Books, not the Kindle app, that seems anti-competitive.
Especially when the user finds out the reason.
If the industry wants better open standards, they the participants should develop those standards and build devices that implement those standards.
What Apple does outside of such standards is nobody else's business - as long as they correctly implement and support the industry standards.
Yes, apple did the R&D to figure out how to let their watch filter notifications by app, and it must have cost them so much to be able to filter notifications that it has to be locked into their watch. That's not them being intentionally anti-competitive, it's just R&D costs, sure, I'm sure it cost a ton to make that private API.
The more cogent argument is that if apple doesn't want their phone to work with smartwatches, they do not have to make it work with smartwatches.
They want it to work with watches so users buy the phone.
If they want it to work with _only_ their watch, then sure, they make more money, but they also harm the user and market in the long-term by making it so competitors aren't on an even playing field.
Do you just kinda believe anti-competitiveness doesn't exist?
Should apple be allowed to make it so you can't communicate with android users at all to increase sales (which they already more-or-less did)? Should they intentionally make it so you can't play the music you purchased on non-apple devices by breaking "iTunes for windows"?
I see no reason it cannot be a private entitlement similar to the other sensitive entitlements on iOS.
If you're astounded by hackers asking practical questions, maybe you should stop carrying water for corps and see how your back feels. Let's talk shop, what are the roadblocks Apple faces here?
This isn't exposing business logic, this is an operating system vendor deciding what it exposes to vendors. There is clearly an API that the apple watch is using to communicate with the OS, why shouldn't other vendors be allowed to access this?
1. Api designed for internal use could take shortcuts and let’s say use secrets that are and should be internal, or run things as root or something.
2. Proper API maintenance includes at least documentation and some kind of update path/schedule. Internally it’s simpler. (E.g. you must be sure not to leak secret stuff in docs)
But in the end I agree with the notion that these changes for Apple are not a huge burden. (Existing behaviour is anticompetitive)
This prevents Apple the platform provider and gatekeeper from giving preferential treatment to Apple the Smartwatch/Headphones/Payment/Entertainment provider
[0] https://developer.apple.com/documentation/bundleresources/en...
[1] https://developer.apple.com/support/compare-memberships/
Apple makes money by selling devices. With giant profit margins, at that.
So why should they be able to charge developers in addition to consumers?
I agree on both side some money needs to be exchanged in terms of features and Apple cant have it all to themselves. But currently it doesn't seems both side is listening and no middle ground. One side wants it all for free, the other side dont want their money and wants to keep everything themselves.
Let's see... How much should Apple pay to the European Union to be allowed to sell devices there? I say 50% of gross income?
They violated the law, so they deserve to be properly disciplined for that.
It's bizarre that you're even framing this conversation in this way - who are you to say how Apple is allowed to behave, and how anti-competitive they deserve to be on the EU market? Are you under the impression that corporations like Apple should wield more power than world governments?
They shouldn't and they don't, but they think they can bully the EU into submission. They wouldn't dare pull this crap in China, they make every concession to be allowed access to the Chinese market. Yet the EU is expected to ask dear Apple for permission to be allowed to regulate their destructive anti-competitive behavior? Insanity.
More like that governments shouldn't dictate such terms and let the market decide - they should just prevent collusion and regulatory capture monopolies.
This is the opposite, an organically grown market share.
It was found to be exactly NOT an organically grown market share in Headphones and Smart Watches.
The DMA identified that Apple owns a significant portion of the playing field for those market (iOS), and modified them to ensure a competitive advantage ONLY for their brands.
This is being rectified now, at least for the EU.
Is there any reason why you're picking your words so carefully as to include "regulatory capture monopolies" but exclude "anti-competitive behavior" as the umbrella term?
Regulating anti-competitive behavior is precisely what the EU is doing with the Digital Markets Act. The EU recognizes that a company does not need to be a monopoly to have severely detrimental effects on the free market.
Net sales: $119575 billion, net income $33916. Margin: 28%
Apple also benefitted from third-party developers writing software for its platform. Remember the "there's an app for that" ads?
I think developers deserve to be treated fairly by Apple, not exploited four different ways. Because to develop for Apple you need:
1. Buy Apple hardware, because Apple doesn't provide cross-platform development tools (unlike Android or even Microsoft).
2. Pay $100 a year just to be able to publish the software.
3. Pay 30% of the app income to Apple (this changed only recently).
4. Have to endure odious restrictions imposed only because Apple wants to keep control of its platform.
This is among the biggest fictions of this crazed argument. Spotify, the company that whines about Apple the most, pays Apple $0 (sorry, $99) for building the entire market for consumer mobile internet upon which their business depends.
You mean, Apple leeches that glomped onto Spotify success to prop up the iOS market share? When not having Spotify meant that people might end up moving to Android? And yet they still required Spotify to pay 30% up until 2022, when the "reader app" exemption was made?
Remember when Apple offered Spotify private APIs for subscription control to work around the iOS App Store piss-poor subscription management?
That Spotify?
The parent is right. Resorting to catch-22s proves how utterly indefensible your stance is.
Please take care to observe the guidelines if you want to participate here: https://news.ycombinator.com/newsguidelines.html
What Apple do slightly differently is that they half-ass the standardization, and then chuck it in the trash. Amounts of efforts spent is within the ballpark.
It is, if we're talking about features designed to boost sales of your other products while preventing competitors from offering those features.
Look, even if they're able to compete fairly, those competitors might remain inferior options for other reasons. But Apple having to compete will make their products better. All of their best achievements came from fierce competition as the underdog. Apple's current situation is not good for it.
Must they get these passed in the standards committees first?
--> If iOS introduces non-standard changes to Bluetooth and Wi-Fi to compete against Android, this does not concern the DMA.
--> If iOS introduces non-standard changes to Bluetooth and Wi-Fi to create a product of ANOTHER market-segment (Headphones, Watches, Routers,...) they are required to provide interoperability for other brands than Apple as well.
The reason is simple: iOS has such a critical size that it is anti-competitive behavior for Apple to modify iOS in order to beat the competition on e.g. headphones.
which is the point here.
If they made a new feature, something AR based, they are totally allowed to build that and keep it relatively private for a few years. What they can't do is when competition appears, actively keep them off their platform. For example if a device manufacturer manages to make an AR device that works well with android, but its impossible with apple and apple have significant market share, then that would be illegal.
The point of this is to stop thiefdoms and to keep innovation. You're allowed to have a competitive advantage, you're not allowed to build a monopoly.
(if we look at defence, budgets are still very high, but the rate of innovation has plummeted compared to other industries. Its only now with the spur of VC cash into non-traditional backgrounds are we seeing innovation again)
Someone at Apple did math on this and it's not worth their time to make this feature interoperable just for the EU market. That's because of this law. They wouldn't have even considered it without the law.
If they refrain from distorting the market in their favor (and instead "retreat and rally up the userbase") the DMA seems to work surprisingly well so far...
The procedures with the EU are quite interesting here, Apple was exchanging extensively for more than a year on how to reach compliance, then the decision [0] was made.
There are also separate procedures for the specification of compliance and investigating (non)compliance.
This gives Apple little room to argue on violation of the DMA later-on, because they were actively involved in defining the criteria beforehand.
So it's possible that they currently just need to find a mode to achieve launch-parity for EU on such features, and they're not there yet.
[0] https://ec.europa.eu/competition/digital_markets_act/cases/2...
There are a few clear precedents where Apple held a feature back in the EU, then shipped later and/or exposed a path others could plug into:
Apple Intelligence: Announced as “not at launch” in the EU in 2024, then rolled out to EU users with iOS 18.4 in spring 2025 (most features). One carve-out remains: Live Translation with AirPods
NFC access for third-party wallets (HCE): After an EU antitrust case, Apple committed to open iPhone NFC (“tap-to-pay”) via Host Card Emulation, let users set a default non-Apple wallet, support Field Detect/Double-click flows, etc., so a genuine “build a platform others can plug into.” The Commission made these commitments legally binding for 10 years.
With iOS 17.4 Apple created EU-only entitlements for non-WebKit engines (e.g., full Chromium/Gecko), so browser makers can ship their own engines on iPhone/iPad in the EU.
Home-screen web apps (PWAs) reversal: Apple initially said PWAs would go away in the EU for 17.4, then reversed and kept them—implemented on WebKit with the usual security model.
Alternative app distribution (marketplaces + web distribution): In response to the DMA, Apple shipped EU-only APIs/entitlements for third-party app marketplaces and later web distribution (direct from developer sites) with notarization, installation, backup/restore hooks, etc.
Tap to Pay on iPhone (SoftPOS): Apple’s merchant “no extra hardware” payments feature expanded across EU countries and is designed for platforms like Adyen/Stripe/Mollie to integrate via SDKs
On the other hand, what is to prevent another ear bud manufacturer writing an iPhone app their ear buds connects to that provides translation? Is this really a hardware feature in the phone? If it’s just software at the phone end, as long as other manufacturers have the feature access to implement this themselves, surely that’s their problem? Why should apple offer translation software as a service to other companies for free? I can see the argument for hardware but not software that others could implement themselves on iPhones.
The only one clearly DMA related with EU specific unlocks are:
* app store
* browser engines
The DMA could have been just an app store regulation. It seems to have had its intended effect there. Very very unproven outside of it. At best you've shown no harm other than delay in some areas.
I'm assuming NFC lawsuits are separate from the DMA but could be mistaken. But in any event NFC payments already existed and aren't a new feature apple decided to release under the DMA.
The upside for the user is to have a larger variety of devices to choose from, each with similar interoperability with his Apple device.
The upside for the market is that all vendors are technically able to compete on the same terms. Apple is not allowed to operate a market, invite others to compete but also participate as a player with preferential treatment.
This is already decided for the existing features of Airpods, Apple Watch, etc. Apple is trying to rally its userbase against the EU by withholding new features now, in hopes that they can secure their skewed playing-field
That is the dream of the dma. It has not been proven to be the reality.
The reality could very well be that EU users just don’t get features. Apple doesn’t have to play ball.
But no, the goal is not to make consumers better off, but citizens and nations better off. And their interests do not stop at $PRODUCT. Namely, they probably don't want a slow slide into serfdom to foreign corporations that abused their market power.
So your belief is that, if DMA didn't exist, Apple still would not ship this feature in the EU?
It's fine if Apple decided to refrain from its anti-competitive behavior in the headphone market because it's not economically viable to have this feature as a generic OS feature.
They know best and are free to do that.
There are huge hosts of software and hardware that work better because of an ecosystem of interoperable components. That’s not anticompetitive, it’s the benefit of good design with compounding returns.
As the manufacturing process and software becomes less complicated, there is a natural trend towards budget competitors (see: SaaS in 2025) that can replicate functionality they know has a market.
The idea that making it unappealing to make an integrated product is good for consumers — or anticompetitive — seems so wrong that it’s farcical. There are definitely cases where verticalization can harm consumers, but this opens the space for good competition. Perplexity wouldn’t exist if Google actually cared about search customers. Internet Explorer didn’t have to be regulated out of existence — by virtue of sucking, there is opportunity.
What they CAN'T do is maintain an environment where their products cannot be met with fair competition by other players, by intentionally giving advantages in the ecosystem only to their own brands.
Apple might not dominate the market for fitness trackers above 150USD today if they wouldn't have prevented others to achieve the same interoperability with their iOS ecosystem.
Apples featureset for wellness tracking was not competitive, neither in function nor in price. Fitbit and Garmin were better in doing that task, but they were not able to display message notifications, apps, etc. because the required interfaces in iOS were only available to Apple's Watch.
Maybe Apple would have beaten them in 2nd Gen, maybe competitors would have followed with equally tight iOS-interoperability in 2nd Gen.
Maybe Apple Watch would nonetheless be the leading Smartwatch in the market today. Or maybe it would be e.g. the Moto360 (google it) just due to Apple's "virtue of sucking" and insistence of doing rectangular watches.
We don't know, because none of the other players are able to compete on fair terms with Apple in this segment until today. And today Apple has such a leap-start that it's questionable whether this can still be rectified.
Let's not pretend like Apple isn't doing everything it can to turn its EU users against their government by complying with the DMA in the most obtuse, disruptive, and useless ways possible. They're risking fines and further punishments betting that they can ultimately subvert the democratic process that put in place laws that would require more developer and user freedom. To Apple, the threat of users owning their computers is an existential one.
Subverting democracy, to me, would involve things like dark money campaigns and lobbying.
The issue is that Apple isn't following the law. It's breaking it and then miming to its customers that its actions are on account of the law. That misrepresentation is meant to convince citizens of the EU that DMA is a bad law with consequences they don't support so that they pressure their representatives to get it removed.
It's Apple making a big show of directly harming consumers as part of a misinformation campaign to get policy that limits their power repealed. To me that reaches the bar for subverting democracy.
The law requires Apple to provide equal access to the iPhone hardware and software in marketplaces that it competes in.
That can be done in a manner that is either additive, by providing access to third parties (which is potentially a significant expense and liability) or subtractive, by choosing not to engage in the regulated activities at all, in that jurisdiction.
In this case they're merely being obtuse by refusing to provide an API to other device manufacturers. Unless you genuinely believe that the cost/benefit analysis of adding a new feature to their OS dictates that they basically freeze development unless they're able to recoup costs by tying it to their accessories, then you must conclude that they made the live transcription API Apple-only, and therefore not DMA-compatible, only to make EU citizens feel like their laws were depriving them of new features.
An organization interested in good-faith compliance would expose their internal API surface with some vetting process for access by interested parties. Then as the API becomes stable they would open it up more broadly. If accused of being anti-competitive by restricting access they could easily and correctly argue that they were working with potential competitors on that stable and secure API, and that their actions balanced the interests of market competition and security.
Of course, Apple is not interested in good-faith compliance. It's my belief that they should be made an example of so that they and other companies running the math in the future decide that proactive and good-faith compliance with regulations is more cost-effective than attempting to fight them.
Inventing a substandard product and using your market dominance in one area to ensure that nobody can compete with your substandard product is as far detached from innovation as you can possibly be. One size fits all solution with centrally planned development where one person knows best and competition isn't considered a driver of progress, isn't that a very communism-shaped approach to "innovation"?
I'm not even joking here and it's bizarre that I'm having to promote the good parts of free market capitalism to someone who claims to care about innovation.
That reminds me of Zukerberg's bluff saying he's going to leave the EU which lasted exactly one day.
But they were found to have already skewed the market with several Apple-accessory-exclusive iOS-features in the past (Proximity pairing, Watch-integration, etc.) and for those they have to provide interoperability now.
They worked with the EU for a year now on how exactly they should reach compliance, then the ruling was made, ordering them to make such interoperability features also available to other brands than Apple.
Now it seems that they try to rally their userbase against that ruling, in hopes to create a political climate that gets the ruling revoked again...
The reality is that, if Apple conforms non-maliciously, they're proving that the law is reasonable and they can do it while remaining profit. Um, that's a huge problem.
They require the plausible deniability of "oh we can't do this, it's too expensive!" Otherwise, other governments (US) might look to implementing similar laws. So, it's a long con. They're burning lots of money, now, with the hope it allows them to continue their anti-competitive behavior for longer. If they're REALLY lucky, they might even stall out the EU and get the EU to backtrack on their laws. That's the golden scenario.
And why not? Apple should be able to "implement OS features for the sole benefit of its own hardware-offering".
With iOS Apple owns the playing field where all accessory vendors compete, and Apple competes on the same field. There is no healthy competition possible if Apple puts the finger on the scale to ensure it always wins.
That's not an answer, it's a decree.
Others can make their own phones and headphones just for their own devices, did Apple stop them?
Not very convincing.
Also, you're confusing markets here. We're not talking about the smartphone market. We're talking about the market of apple accessories.
Apple solely controls that market and also participates in it. Its a true monopoly.
Doesn't mean it's an answer to the issue why that should be the case.
Was that an unearned position due to regulatory capture or something, or did people buy their stuff, even if it's more expensive?
Is it even a dominant position with no recourse? (last I heard Android has more share in the EU and the world). Did they collude with Google and other smartphone vendors to not allow them to build and allow similar features themselves?
>With iOS Apple owns the playing field where all accessory vendors compete, and Apple competes on the same field
Isn't that playing field their own OS and device ecosystem, they build?
> Isn't that playing field their own OS and device ecosystem, they build?
That playing field is their own OS, and the entire ecosystem of all accessory brands.
Thats would involve exposing public api ie “a burden”
A duelist was found to arrive with a gun to a knife-fight and is asked to either allow everyone a gun or use a knife.
Now we're arguing that it's a burden to him because bringing a gun is his innovative approach to win knife-fights, and making it a gunfight or keeping it a knife-fight is hindering the innovation he brings.
Apple OWNS the terms for this fight. If they believe that their fights should evolve to be gun-fights then all players should have guns.
It was decided that they can't continue restricting guns while shooting all knife-duelists, at least not in the EU.
The EU stepped in and said that they can't distort duels like that any longer
I recommend you to read the ruling [0] and form your own opinion.
> The EU wants Apple to happily accept a burden that makes it harder to produce the products that made it popular in the first place.
No, the EU mandates that Apple cannot implement OS features for the sole benefit of its own hardware-offering in a different market, because this is not fair competition. They are not required to foster new HW ecosystems for each feature, they just have to provide access to such OS features under equal conditions:
[0] https://ec.europa.eu/competition/digital_markets_act/cases/2...