Average users have used Uber or a transit app to purchase a ride. And ordered a meal.
I’ve never heard of users disputing their Uber rides or food deliveries with Apple - have you?
Slapping a “this transaction will not be processed and receive no support from Apple” is otherwise enough to reemphasise the point.
You and I have been over this a million times. Amazon, Uber and food delivery aren’t the same as digital in-app purchases. When you buy a ride, a physical product, or a meal, the transaction is fulfilled outside Apple’s ecosystem you physically see the package, car or the food, and you know you’re dealing with Amazon, Uber or DoorDash.
Digital goods are different: the entire transaction happens inside the iOS environment, and for almost 20 years users have been conditioned to expect Apple’s guardrails there: refunds, parental controls, fraud checks. A disclaimer won’t undo that expectation. If something goes wrong, people will still say “I got scammed on my iPhone and Apple wouldn’t help.”
That’s why Apple insists on a single system for digital goods. It protects the brand promise and gives every user the same trusted experience.
Quite the irony, given how many/most other apps are paying nothing except a yearly flat fee.
The revenue share only kicks in when an app monetizes digital goods inside Apple’s ecosystem. Apples rules are clear: if you’re doing that, you owe Apple on top of the yearly fee. If you don’t want to do that, then you don’t have to.
Epic can’t just skip paying its server bills because some other customer gets a better deal or the server company donates server use to a non-profit.
They aren’t “using” anything when unlocking a virtual helmet or in-game weapon, once the app has been delivered to the customer’s device. Except, in some instances, Apple’s IAP - which they do not want to use.
Sure, some developers don’t want to use Apple’s payment system. But the reason Apple requires it is because customers benefit from consistency. One set of APIs means every purchase runs through the same fraud checks, parental controls, refund process, and security model.
If Apple let each app decide, the user experience becomes fragmented, less safe, and worse overall for everyone. You’d have one app using Apple’s rails, another dumping you into a random web form, another storing your card on their servers, and a bunch selling your data. Most users won’t spot the difference outside of “this is more annoying than it used to be” but when something goes wrong, they’ll blame Apple.
Imagine if every time you downloaded a new app you had to create an account, give your personal info and hand over payment details - that’s what you’re advocating for. It’s much better for users to have everything go through Apple. You get subscription reminders, easy cancellation, privacy, etc. I understand why developers don’t like that, but I can’t fathom why end users should suffer so the Epics and Spotifys of the world get to freeload and then sell your data on top of it.
And the fact of the matter is developers are not forced to use IAP. If they don’t want to use it, they can (and do) push people to the web, like Netflix and Spotify.
And the court agreed that Apple, a company with monopoly power, can’t force them to use it or prevent them from linking out to alternative purchase options.
The court explicitly ruled Apple didn’t have a monopoly, and only said they must allow link outs after misinterpreting California law.