Apple’s announcement says EU developers will get new terms for alternative distribution. The headline change is that the old Core Technology Fee, which charged per install after scale, becomes a 5% Core Technology Commission on digital transactions for apps distributed outside the App Store. Apple also says it is dropping the initial acquisition fee and store services fee, while keeping notarization for every alternatively distributed app. For App Store apps that send users to the web to buy digital goods, Apple says it will still charge 15%, or 10% for some smaller developers. Reader apps such as Netflix and Spotify also appear to get a bit more freedom to promote outside offers in the EU.
Most reactions were hostile because the basic power structure barely changed. Apple still decides what can run through notarization, still keeps a cut of non-Apple payments, and still sits between developers and users even when distribution happens on the web. The strongest practical point was that this looks less like compliance with the Digital Markets Act and more like Apple replacing a legally vulnerable fee with one that is easier to defend and easier to self-report. Several people also noticed the press release claims these changes “resolve” disagreements with the European Commission, but there was no matching Commission announcement. That left a lot of skepticism that Brussels has actually signed off rather than simply continuing the process.
Where the conversation landed was blunt. If your standard is “slightly better than before,” this is progress. If your standard is “a phone owner should be able to install software without Apple’s permission and a developer should be able to sell digital goods without Apple taking a cut,” this is nowhere close. The bigger divide was not over this fee schedule but over what a smartphone is supposed to be. One camp treats the iPhone as a general-purpose computer whose owner should control code execution, much like a Mac. The other treats centralized control as an acceptable part of the product, either for convenience or security. Even among people who value the App Store’s simplicity, there was little belief that Apple’s review system meaningfully protects users from scams well enough to justify permanent gatekeeping.
If you build consumer software, treat the EU changes as a pricing and distribution tweak, not a true opening of iOS. Watch for whether the European Commission formally signs off, because the practical ceiling on competition is still Apple's review and transaction leverage.
Strongly negative toward Apple, with frustration that the EU may accept cosmetic changes while leaving Apple’s control intact. The main reasons were continued notarization, continued commissions on non-Apple payments, and doubt that the Commission has actually approved the arrangement.
Key insights
01
The new 5% fee likely relies on self-reporting
The commission on web-distributed apps appears to be tracked largely through developer reporting rather than through Apple’s checkout flow. That makes this less a technical opening than a compliance regime, with the real risk shifting to audits, bans, or automated accusations when Apple thinks revenue was underreported.
If you use EU web distribution, plan for revenue reporting and dispute handling as seriously as payments. The operational burden may move from integration fees to compliance risk.
The wording in Apple’s release says the changes resolve disagreements with the Commission, but commenters could not find a corresponding formal EU statement. The more plausible read is that Apple is framing an ongoing negotiation as settlement, and private lawsuits under the Digital Markets Act could still test the model even if regulators tolerate it for now.
Do not treat this press release as the final legal state of play. If your business depends on EU iOS economics, wait for explicit Commission language and expect further challenges.
Apps like Netflix and Spotify appear to gain permission in the EU to promote outside offers without an actionable link. That is not open commerce on iOS, but it does loosen one of Apple’s more rigid anti-steering rules for subscription media apps.
If you run a reader app, revisit your EU in-app messaging and pricing funnel. Small wording changes may now be worth real conversion lift even without direct checkout links.
Several developers pushed back on the idea that Apple’s full software ecosystem is what creates app value. Cross-platform frameworks like Flutter, or custom stacks that mostly need graphics, input, networking, media, GPS, and other baseline OS services, make Apple’s claim to ongoing revenue participation look weaker for a large class of apps.
If you build on cross-platform tooling, map exactly which Apple-specific services you truly depend on. That dependency analysis matters both for cost exposure and for future policy arguments.
People defending Apple’s gatekeeping leaned on user safety, especially for less technical users. The rebuttal that stuck was that the App Store is already full of scammy subscription apps and misleading search results, so review does not earn the sweeping trust Apple asks for. That weakens the case for tying security to exclusive distribution control.
Do not assume users or regulators will keep accepting “review equals safety” as a sufficient argument. Product teams should expect more pressure to separate sandbox security from store control.
A real minority view held that consumers do not care about developer economics and mainly want a simple, centralized place to get apps. For those users, the risk is not Apple’s cut but adding side-loading paths that make social engineering and malware installation easier, especially for less technical family members.
If you argue for more open distribution, pair that case with concrete user-protection flows. Convenience and fraud resistance still matter to a large non-technical audience.
One defense of Apple’s model was that charging developers may reduce pressure to raise device prices, similar to a razor-and-blades business. Others disputed whether Apple can really shift prices that way, but the point highlights that platform taxes and hardware pricing are linked in how some people think about the market.
When modeling platform policy, account for how incumbents will frame tradeoffs to consumers. Arguments about openness often lose when they sound like benefits for developers only.
Some commenters rejected the idea that Apple owes developers or users a fully open iPhone. Their view is that nobody is forced to buy an iPhone or build for iOS, and Apple’s refusal to help install arbitrary code is not the same as preventing device modification outright.
Expect any policy push for open mobile computing to run into a strong property-and-choice argument. Winning that fight requires more than proving Apple is extractive.
apple.com