That argument would assume no cost for upgrades.
I remember having to buy new operating systems.
That said, looking at the state of recent OS upgrades, I think I'd have been happy if the only changes over the last, oh, decade or so, had been purely security updates. But these too are not free.
> Apple wants to double-dip and charge developers for the value that the users already have by virtue of owning their iDevices with all the necessary iOS paraphernalia in them.
Yes, obviously they want to make as much money as possible, and this is at odds with consumer interests.
That said, I have the impression that for many users, the benefit is the app ecosystem, while for many developers the benefit is the users. Endless marketing cycles of new-shiny-API for one, and new-shiny-UI for the other.
That said, power-law distribution, so "the app ecosystem" is probably mostly Meta, Google, Amazon, as specific names, then becoming somewhat vague with "whatever work mandated of Slack or MS teams", "their bank", "three or four supermarkets", and "a taxi firm who may or may not be Uber".
It's not at odds with consumer interests at all. It's at odds with developer interests.
It would actually cost consumers more if Apple couldn't make any money from developers directly because they'd try to make it up by charging more for Apple products.
Developers might prefer to shift the burden to consumers's wallets instead of their own, but overall this model is beneficial for everyone involved. It is also better for the environment because directly making money from developers incentivizes them to support old hardware for as long as possible.
I vigorously disagree with this. It sounds very confused about economics, specifically prices.
Apple, as every market actor does, charges the absolute maximum price the market will bear for their products and not a penny less. They cannot "make up" any money that comes from unrelated parties (such as their Google payola for search, or their casino games for children IAP revenue) by raising product prices. If they could raise their product prices and have that be profit-positive, they would have done it yesterday.
They could raise prices on phones to make up for a hypothetical "free iCloud+," because the same consumers are the other party in both those transactions so presumably many people would see that the more expensive phone justifies free iCloud services.
Apple doesn't set its prices by saying "OK, we need exactly 83 billion dollars in net income this year, so given that our products cost us 233 billion dollars to make and we have 54 billion dollars in expenses, we need 383 billion in revenue, so now let's set prices of each product to target this."
That $83 billion in net income is just the number they are able to make last year with the prices being what the market would bear. Trying to increase prices to hold it there when a downfall in other revenue happens would depress sales.
That price is much lower than it otherwise would be if the only revenue Apple could generate came from hardware. The opposite incentive exists today, where it actually benefits Apple to sell cheaper razors to make more money from the razor blades.
Not entirely how you've made formed this connection but respectively it sounds like you've confused several things here.
iPhone sales pay for the entirety of Apple's R&D. 10 times over.
Android is moving to the same, KYC (credit or debit card; no prepaid cards) with play store required for APK distribution
Which censorship do you consider problematic?
The app is still available in Russia on both App Store and Play Store.
[1] https://blog.google/company-news/inside-google/company-annou...
The only change made that's relevant to sideloading-a-downloaded-APK as far I understand, is a 24hour delay in enabling the ability to do so, which is a wildly overblown non-issue.
Availability is a key component of security, and this is a 24-hour DOS on apps not blessed by google.
It will likely be delayed, just like Manifest v3, but eventually it will happen.
> “Following today’s announcement, the Commission will monitor Apple’s effective implementation of the new terms,” it added.
There's nothing on the commission webpage, all I could find is the above comments from a spokesperson which aren't hugely definitive.
I think we can take the mention of dialogue to mean the commission thinks the new rules are a step forward enough that wider civil society can have a look and maybe kick up a stink, and the absence of press release coordinated with Apple as evidence the procedure is still open
This press release conspicuously lacks any suggestion that it did agree.
> [“The Commission welcomes the changes made by Apple to its commercial terms,” commented a spokesperson for the European Commission. This announcement, the spokesperson continues, is “the result of close dialogue between the Commission and Apple,” after the tech giant was found in April 2025 to have breached the rules of the Digital Markets Act (DMA) and ordered to take the necessary corrective measures. In light of these developments and the changes to be introduced, “the Commission will monitor Apple’s effective implementation of the new conditions.”](https://www.eunews.it/en/2026/08/18/tracking-and-new-commerc...)
How do you not use their SDK?
The first third party iPhone apps existed before the SDK existed. iPhone OS was jailbroken pretty quickly and apps emerged fast. SDKs are nice references and tools but the're not the only way to skin a cat.
If you think the header files are the thing that Apple thinks is worth of a cut of app revenue, I think you're way off base. It's the technology, whether you access it with permission or not.
This seems like a very large and unfounded assumption on your part, particularly in a world where we no longer pay for Apple operating systems or their updates.
That's your claim. Neither Apple nor the EU appear to agree. Nor do US courts appear to agree in the Epic v. Apple trial.
Apple itself has to pay license fees for some technologies in iPhone, and those licenses do not automatically extend to third-party developers via the consumer. It's not a license agreement with the consumer.
When you said, "there's no way to signal to Apple that you have opted out of using their SDK and have the fee waived", which fee did you mean exactly? The quote in your comment refers to the Core Technology Commission, which is a percentage of app revenue. There's also the $99 developer program fee, which all App Store developers pay.
I know that some developers are annoyed by the $99 fee, but for professional iOS developers, $99 is a drop in the bucket, and the revenue % cut is the vastly larger and more important thing. So if by "the SDK" you mean only the header files and such, that seems like mostly a red herring to me, and if you were allowed to use the technology for free, then there wouldn't be much reason for Apple to charge for the SDK. And indeed, Xcode has always been available for free. https://apps.apple.com/app/xcode/id497799835?mt=12
This point was never raised in any of those cases. Apple just did aome hand-waving "IP compensation" justification and everyone just went along with it, because the case wasn't about that particular point.
> Apple itself has to pay license fees for some technologies in iPhone
And such costs are more than made up for by hardware sales. The only reason this persists is because of greed, not because it's essential to profitability.
> and those licenses do not automatically extend to third-party developers via the consumer. It's not a license agreement with the consumer.
They don't need to extend them because the consumer is already entitled to use those technologies merely by having purchased the device. That entitlement comes from the fact that they get legal copies of the technologies when they take posession of the hardware. IP rights regulate distribution, not consumption.
As for the rest of your comment, the overall problem is the requiremet to deal with Apple at all, the $99 fee and the 5% commission are just the cherry on top.
I strongly disagree with your interpretation. IP compensation was essential in both of these cases, and everyone went along with it because they didn't dispute Apple's rights.
> IP rights regulate distribution, not consumption.
It's all about distribution.
A consumer can download Xcode, build their own app, install the app on their own device, and use Apple API, all for free. What they can't do is distribute that app to other consumers.
The developer tools are relatively unimportant, which is why Apple gives them away. Distribution is everything.
> As for the rest of your comment, the overall problem is the requiremet to deal with Apple at all, the $99 fee and the 5% commission are just the cherry on top.
This doesn't answer my question. I asked which fee needed to be waived. There is no fee to get Xcode, so there's nothing to be waived by opting out.
I was referring to the distribution of the licensed technologies by Apple to the hardware purchasers. Returning to your own interpretation though, the hypothetical community SDK wouldn't contain proprietary code, so the distribution aspect is solved there. It's the same principle by which homebrew game console scenes work, or how you can build Windows software on Linux without touching any Microsoft code.
> This doesn't answer my question. I asked which fee needed to be waived. There is no fee to get Xcode, so there's nothing to be waived by opting out.
The waiver scenario is meant in the context of Apple using the 5% and $99 fees as payment for the maintenance/R&D of the official dev experience. The fees would be waived because the dev isn't making any use of those tools in a hypothetical FOSS SDK.
I know. My point was that distribution of the licensed technology by Apple to iPhone purchasers does not thereby allow third-party iPhone app developers to distribute their iPhone app executables to other iPhone purchasers.
> Returning to your own interpretation though, the hypothetical community SDK wouldn't contain proprietary code, so the distribution aspect is solved there. It's the same principle by which homebrew game console scenes work, or how you can build Windows software on Linux without touching any Microsoft code.
You appear to be focused on the building of iPhone apps. I'm focused on the distribution of built iPhone apps. This is why I said, "The developer tools are relatively unimportant, which is why Apple gives them away. Distribution is everything."
In general, consumers are unwilling or unable to build their own apps. They need precompiled executables, distributed by third parties, to easily install on their devices. The hypothetical FOSS SDK is a red herring. I don't see how the consumer's right to use the iPhone automatically grants a legal right for third-party developers to distribute executables using Apple's licensed technology. There are other consumer products that allow personal use but don't allow redistribution.
Unfortunately when it comes to technology licensing, it is rarely successful to say you should pay less because you purposely made your job harder.
I don't intend to insult you, but as an iOS developer myself I have serious doubts about whether you have any expertise in the subject you're talking about here.
That's not really the issue. LLM participation is a red herring. The issue is "replicates the original's functionality".
It's you who has started to argue by replying to my comment in the first place.
Your answer seemed nonsensical to me.
What I meant, though, is that I'm not going to argue about a specific point, the viability of "some FOSS SDK that perfectly replicates the original's functionality." If you don't even have any experience with iOS development, then you have no basis for making any claims about that subject, and thus I'm not going to bother explaining "What would be so outlandish about that?"
In any case, most iOS devs don't want to opt out of using the SDK. That would not be a particularly attractive route for making iOS apps. What I want as an iOS dev is the same freedom of software distribution that we have on macOS.
The basis for my claims about the subject is my knowledge of computing and development in general. I dipped my toes into iOS dev a few times and there's nothing that seemed to set it apart from any other SDK situation beyond Apple's restrictions, at least nothing that would make my claim outlandish.
Core device apis yes, everything else, maybe not?
I think we could roll our own UI - I think we can roll our own payment systems - I think we could roll our own media display.
For the primary iOS app I work on I need vulkan, gps, touches camera, sound, and phone rotation. (And standard os services)
I don’t need anything else.
Basically enough to render inputs to a gpu accelerated surface.
And I'd argue that this is a core OS feature that you expect on any modern OS.
> Basically enough to render inputs to a gpu accelerated surface.
I suspect it uses much more so that it can support
- audio
- file I/O
- accessibility
- …
Absolute power corrupts absolutely, and now they've attained it, they won't give it up voluntarily. You have to force them.
The app developers can offer their own line of devices on the market. Users are free to choose a different manufacturer. Apple doesn't hold anybody in chains, it is people and developers who are coming to them.
Or should people to restaurants and demand to be allowed to order food delivery from other places to their tables, and bring their own drinks? Honestly, I think that most hackers and EU bureaucrats think that it would be a splendid idea.
A restaurant is private property, you're just a customer in someone else's turf. An iPhone (and the individual iOS copy inside it that provides the advertised functionality) is the intellectual property of Apple, but also the private property of the user, and it is the traditional property ownership status that determines who gets to interact with the functionality. Apple is unfairly forcing themselves into the dev-user relationship here.
> Apple is unfairly forcing themselves into the dev-user relationship here.
Who was forced to buy an iPhone? Who was forced to develop for Apple devices?
No, because Apple chooses to prevent me from controlling the device the way I want. The skill involved is about finding holes in the system, not in enabling an "expert mode" or something.
The imbalance of power is itself a problem. A hardware manufacturer should be legally prohibited from designing their devices in such a way that they retain more control over them post-sale than the actual owner. Device ownership should mean maximum control over code execution.
> Who was forced to buy an iPhone?
Nobody, but I'm not a free market absolutist.
> Who was forced to develop for Apple devices?
Every developer who wants to cater to ~half of the mobile user population (~85% if it's young Americans)
That's a pretty ridiculous argument if you ask me.
Apple on the other hand offers a locked down product that many people want because they don’t trust themselves. I think a lot of people have short memories for all the hacking and spyware that plagued Windows users a couple decades ago. I think we also need to remember that Apple is not the government so people have alternatives to buying their devices.
Personally, I think people should have the right to buy a locked down device. It’s not on Apple to provide open competitors to their product. And why should developers have a right to develop for the platform? Heck, I wanted the iPhone back when it didn’t even have 3rd party apps at all.
The idea that, for many people purchasing an iPhone, the inability to install apps from alternative stores or the web is a selling point seems rather questionable.
On top of that this could easily be provided by an optional switch that enables you to enforce this on your own device if you so desire.
It is a poor reason to request that all app distribution for everyone else also has to go through Apple and its terms, basically for your convenience.
And that still plagues every computing platform now. Including Apple platforms. So the lockdown clearly didn’t completely solve that problem like a lot of people seem to claim
They have no power to prevent you from doing anything you want to your device. Just like Ford has no power to stop me from modifying my truck in any way I want. Or any other product from any other company.
Not helping you is something different, that's not preventing.
> Every developer who wants to cater to ~half of the mobile user population (~85% if it's young Americans)
That's a choice for them to make. You might then say that Coca-Cola is forcing supermarkets to carry their product because customers want to buy them.
They have the technical ability to prevent me from running the code I want, and they exercise that ability for that purpose. They're not a passive actor in this situation, they explicitly block me from doing things that they themselves can do, even after the sale.
Again, this should be a concern merely because of the power imbalance.
> That's a choice for them to make. You might then say that Coca-Cola is forcing supermarkets to carry their product because customers want to buy them.
Not the same thing at all. The mobile app market is a top-level one in a way the Coca-Cola one is not. Apple is controlling a huge amount of commerce for products that have nothing to do with them, besides being digital accessories to iDevices.
The better analogy would be: there are only two store companies in the entire US. If you want to sell any product at all, of any category (silverware, food, lawnmowers etc) you must contract with them and there's no other way, and anyone who wants to purchase any product whatsoever only has those two options.
You are effectively forced to buy either and Android or an iOS phone to participate in society.
Since the market for phone operating systems is not even remotely competitive regulation is necessary just like in all others uncompetitive markets.
And now you are saying that people were forced to purchase iPhones because of Android?
> which unfair market conditions made it impossible
Bank applications depending on various os or device level security features? Good luck getting developers to build applications for your platform in general until you have a very large number of users (even Microsoft couldn’t manage it when the oligopoly was way less entrenched)
Well then you aren't forced to purchase an iPhone, are you? Much less forced to develop for an iPhone. If a developer isn't satisfied with having access to billions of Android customers, then they should change careers or stop complaining.
Developers also had every opportunity in the world to offer their software for Windows Phone and BlackBerry devices. Or offer their own devices with their software. Which is an easy thing for banks to do. Their laziness and incompetence isn't an excuse for them to turn around and point fingers at Apple for being successful. They made their own bed.
> Users are free to choose a different manufacturer
It’s an oligopoly, so no, consumers are not exactly free to do what they want. If the market were truly competitive you might have a point.