Skip to content
AppDues
Log in
Contact salesSign up

Epic vs. Apple: what the ruling means for app developers

Judge Yvonne Gonzalez Rogers ruled on September 10 in the Epic vs. Apple case. Epic prevailed on one count, and the resulting permanent injunction became the part of the decision with the widest consequences for developers. This guide separates what the injunction clearly changed from the implementation questions it left open. It is general information, not legal advice.

What the injunction actually changed

The injunction barred Apple from blocking developers from doing two things: adding buttons, external links or other calls to action that send customers to purchasing options alongside in-app purchase, and communicating with customers through contact details obtained voluntarily during in-app account registration.

That is narrower than a general right to replace in-app purchase. It is best understood as an anti-steering change: developers could point customers toward another purchasing route, while the in-app purchase system itself remained in place for purchases made inside the app.

Direct card charging inside the app

No. The change affected a limited part of section 3.1.1 of Apple's App Review Guidelines. For most apps, in-app purchase was still required for transactions completed inside the app. The expected practical change was permission to direct customers outside the app to pay on a website.

Reader apps such as Kindle and Netflix were different because they already did not need to offer in-app purchase. They could potentially link out to their own websites without adding Apple's payment system. Other developers could add a web route, but could not simply drop in-app purchase and charge cards in-app instead.

Browser, webview, or deep link back?

The injunction did not settle this point, leaving it to Apple's interpretation. The article's prediction was that Apple would not permit external payment inside an in-app webview, because a webview can look like part of the app and blur the distinction Apple wanted to preserve.

For planning purposes, assume a customer leaves the app for Safari, completes payment on the web, and is then returned to the app through a deep link. Build the return path and entitlement recognition before relying on the external route.

How many links, and how prominent?

Apple could introduce limits on how many external-payment links appear and how they are presented. The extreme possibility discussed was a single plain-text link, although the injunction's plural wording — links, buttons and calls to action — made that outcome questionable.

A Kindle-style example shows why the detail matters: one link to a retailer's homepage is very different from a catalogue where every book carries its own purchase link. The article expected Apple, at minimum, to require an external-payment prompt to be less prominent than the in-app purchase prompt on the same page, with reader apps possibly exempt.

Could Apple require the same price everywhere?

Apple had once required in-app subscriptions to be priced the same as or lower than the same subscription elsewhere, then dropped that requirement in 2011. Nothing in the injunction itself stopped Apple from reviving price parity.

However, the judgment found that Apple unreasonably restrained competition by withholding information that could help consumers find cheaper prices, better service and more options. Forcing identical prices everywhere would sit uneasily with that reasoning, so the article treated mandated parity as unlikely.

Could Apple take commission on external sales?

Yes, according to the judgment's reasoning. In-app purchase is the mechanism Apple uses to collect its licensing fee, and the court said Apple could still charge a commission without it — collection would simply be harder.

The article nevertheless predicted Apple would not levy such a commission. Collecting from a long tail of small developers would be administratively difficult, and Apple already allowed access to content bought on other platforms without taking a commission. The Uber example made the same point: a service can depend on Apple's intellectual property, such as GPS, without paying Apple a commission.

United States only, or global?

The injunction applied only in the United States. Whether Apple would keep different rules by country or apply changes worldwide was unresolved.

The article predicted a global approach, citing a recent precedent: after settling with the Japan Fair Trade Commission on September 1 to let reader apps provide a single link for creating and managing accounts, Apple applied that change globally even though the settlement was Japan-specific.

Timing and the appeal

The injunction was due to take effect 90 days after it was issued, on December 9. Apple filed an appeal within hours of publication of the original article and asked for a stay, with that request expected to be decided in November. A successful stay would delay the injunction until appeals finished, or the injunction could be overturned; the appeals process could take years.

One argument for overturning was that the injunction rested on California's Unfair Competition Law, a state law, yet applied nationwide.

Who benefits?

Both sides have something to lose. Consumers benefit from Apple's controlled approach to purchases, refunds and subscription management, and developers benefit from low-friction checkout plus payment details customers are more likely to keep current on their Apple account.

But the existing model also blocks viable low-margin businesses — ebooks or music, for example, may not work with a 30% commission — and forcing a customer into a browser to buy a Kindle book is a worse experience than buying in the app. Developers also cannot refund customers directly when Apple owns the payment relationship. The article's conclusion was that choice itself has value: let customers pick between App Store convenience and potentially cheaper alternatives, and let developers try to recover a few points of margin, even though the full gap between Apple's commission and roughly 3% card fees is unlikely to be captured.

Not the end of the story

No. Several other processes were already under way:

  • South Korea had enacted a law barring app store operators from requiring their own payment systems, with Apple and Google due to submit compliance plans by mid-October.
  • The Dutch antitrust authority was reported to have found Apple's mandatory in-app purchase rules anti-competitive.
  • The European Commission had preliminarily found Apple abused its dominant position in music streaming by mandating in-app purchase, with alternative app stores among the possible remedies.

Outcomes there were even less certain than in the Epic case, and regulators were expected to watch Apple's response closely.

How subscription developers should prepare

Use this checklist before building an external-payment route:

  • Keep in-app purchase in place; external payment supplements it rather than replacing it.
  • Assume the customer must leave the app for a browser and return by deep link after purchase.
  • Prepare for limits on link count and prominence, and design the in-app purchase prompt to remain at least as prominent.
  • Do not assume price parity will be required, but do not build a business case that depends on it.
  • Do not assume Apple will take commission on external sales, but keep that risk in the model.
  • Build web account management, cancellation and billing-update flows if you do not already have them.
  • Time experiments around the December effective date, while tracking the appeal and any stay.
  • Keep the external route compliant with Apple's rules as they are published, rather than designing around them.

Teams already selling web subscriptions could test sending customers from the app to the web once the permitted link formats became clear. Teams without web sales first needed the underlying infrastructure. For a hosted web paywall option, see {{OWNER_WEB_PAYWALL_OFFER}}.

Frequently asked questions

Can developers now charge cards directly inside the app instead of using in-app purchases?

No. The ruling removed a narrow part of the anti-steering restriction, but in-app purchase support for activity inside the app was still expected to remain. Reader apps were treated as an exception because they already did not have to offer in-app purchases.

Will linking out use a browser or an in-app webview?

That detail was left to Apple's interpretation. The practical planning assumption in the article was a move out to Safari, completion on the web, then a return into the app, rather than an in-app webview.

What limits might Apple place on external-payment links?

Apple might limit how many links appear and how prominent they are, possibly requiring an external-payment call to action to be less prominent than the in-app purchase option on the same page. Reader apps could be treated differently.

Could Apple require price parity between in-app and web purchases?

Nothing in the injunction itself barred such a rule, but the judgment criticised preventing developers from telling customers about cheaper web prices. Requiring identical pricing everywhere was therefore considered unlikely.

Can Apple charge commission on external purchases?

The judgment said Apple could charge a commission even without in-app purchase, because in-app purchase is how it collects its licensing fee. The article predicted Apple would not do so, citing collection difficulty and existing commission-free access for content bought elsewhere.

Will the rules apply globally?

The injunction itself applied in the United States. The article predicted Apple might apply any new rules more widely, pointing to its earlier Japan reader-app settlement being applied globally.

When would the changes take effect?

The injunction was set to take effect 90 days after issue, on December 9. An appeal and possible stay could delay or overturn it, with the appeals process potentially taking years.

Would the new rules help consumers or developers?

Consumers gain transparency and possible lower prices, while developers gain a choice of payment route. Against that, in-app purchase offers familiar refunds, subscription management and payment-detail updates, and moving to a browser can worsen the buying experience.

Is this the end of the story?

No. South Korea, the Netherlands and the European Commission were all pursuing related measures at the time, and regulators were expected to watch Apple's response closely.