Apple’s App Store fight is back in the slow lane — and developers should plan for uncertainty

Technology reporting: Apple’s App Store fight is back in the slow lane — and developers should plan for uncertainty

Apple’s most useful development today is not a new iPhone feature, a Mac spec bump, or a services bundle. It is a procedural move in the long-running Epic Games v. Apple case that could determine how much freedom U.S. iOS developers actually have when they steer customers to web payments.

The change: Epic has opposed Apple’s latest effort to pause lower-court proceedings over external-link commissions while the Supreme Court reviews part of the case, according to 9to5Mac reporting published July 13, 2026. Apple, meanwhile, already has a live Supreme Court case. The Supreme Court docket shows that the Court granted certiorari on June 30, 2026 in Apple Inc. v. Epic Games, Inc., limited to one question about civil contempt and whether a court may punish a party for violating an injunction’s “spirit” when the injunction did not expressly spell out the precise conduct at issue.

That sounds like legal fog. For developers, it is much more practical: the fight is about whether Apple can charge a commission, and under what constraints, when an app sends a user outside the App Store’s in-app purchase system. For users, it is about whether “pay on the web” actually means cheaper or more flexible choices, or whether it becomes another checkout path wrapped in rules, reporting obligations, and platform fees.

What changed today

The new reported move is Epic’s opposition to Apple’s request to stop lower-court commission proceedings while the Supreme Court considers Apple’s appeal. 9to5Mac reports that Epic argues Apple is trying to delay competition with its in-app purchasing system and that the lower court still needs to determine an appropriate commission even if the Supreme Court later reshapes the civil-contempt ruling.

One important caveat: the Supreme Court docket is public and confirms the larger appeal, but the specific lower-court opposition filing described today was not independently retrieved from a public court document in time for this report. That part is therefore attributed to 9to5Mac’s reporting rather than treated as directly observed filing text.

The verified Supreme Court record is clearer. In docket No. 25-1311, Apple filed a petition for a writ of certiorari on May 21, 2026. Epic filed its opposition on June 4. Apple replied on June 9. On June 30, the Court granted the petition, but only as to Question 1: whether a court may hold a party in civil contempt based on a violation of an injunction’s “spirit” where the injunction is silent as to the conduct at issue, or whether contempt must rest on a clear and unambiguous order that proscribes the precise conduct.

A related emergency track also matters. In docket No. 25A1213, Apple asked Justice Elena Kagan to stay the Ninth Circuit mandate on May 4, 2026. Epic responded on May 6. Justice Kagan denied the application that same day. That denial did not end the case; it meant Apple did not get emergency relief at that stage.

Apple’s framing

Apple frames the case as a question about the limits of judicial power, not as a simple referendum on App Store fees. In its Supreme Court petition, Apple argues that civil contempt should require violation of an order that clearly and unambiguously prohibits the precise conduct at issue. Apple says the Ninth Circuit’s approach allowed contempt based on the “spirit” of an injunction rather than its text.

That framing is not trivial. Civil contempt is a serious tool, and Apple is trying to make the case attractive to justices who may care less about Fortnite or app-store economics than about injunction clarity. Apple is also trying to separate the Supreme Court question from the broader public fight over whether its App Store business model is too restrictive.

Apple’s practical position has been consistent: the App Store provides distribution, trust, commerce infrastructure, security review, and discovery, and Apple believes it may charge for those benefits even when a transaction is completed elsewhere. In European Union documentation, Apple makes a similar value argument, saying the App Store commission reflects distribution, discovery, secure payment processing, commerce services, fraud prevention, customer support, and other tools. The EU regime is not the same as the U.S. litigation, but it shows the pattern: when regulators or courts force more outside-payment flexibility, Apple tends to preserve a fee structure and compliance layer rather than simply stepping away.

The independent evidence

The official record does not support a clean “Apple lost everything” or “Epic won everything” headline. The Supreme Court has not yet ruled on Apple’s contempt argument. It granted review only on one question, not the entire App Store model. The May emergency stay was denied by Justice Kagan, but emergency denial is not a merits ruling.

The lower-court history, as reflected in the Supreme Court filings, is sharper. Apple’s petition says the case concerns whether the Ninth Circuit properly upheld civil contempt after Apple adopted a system that allowed external purchase links but imposed conditions, including a commission and link-presentation limits. Epic’s opposition calls Apple’s behavior a scheme to violate the 2021 injunction and cover it up. Those are adversarial claims, not neutral findings by themselves, but the Ninth Circuit decision below is the reason the case reached the Supreme Court.

The most useful reader takeaway is that the current fight is not merely about whether a button can link to a website. It is about whether Apple can make that button economically weak enough that many developers keep using in-app purchase anyway.

That is the same competitive hinge regulators have been testing in Europe. Apple’s EU developer documentation now allows more communication and promotion of external offers for apps distributed on the App Store in the EU, but developers must use specified entitlements and StoreKit External Purchase APIs, report external purchase tokens and transactions, and pay applicable fees and commissions. Apple’s EU page lists reduced in-app purchase commission structures, optional payment-processing fees, initial acquisition fees, store-services fees, and, under some terms, the Core Technology Commission. The details vary by agreement and storefront, but the direction is unmistakable: Apple is opening doors while keeping toll gates and reporting pipes attached.

Why it matters

For large developers, this case could affect real margin. A streaming service, game publisher, dating app, creator platform, or productivity app with meaningful web billing can absorb legal review, build external checkout flows, reconcile taxes, support refunds, and report transactions. If the court ultimately limits Apple’s ability to impose external-link commissions or presentation restrictions, those companies have the most to gain.

For small developers, the upside is more conditional. External payments can avoid some App Store costs, but they replace Apple’s system with payment processing, fraud handling, customer support, tax compliance, refund flows, subscription recovery, and legal uncertainty. If Apple can charge a high commission on external purchases, the math may not justify the engineering and compliance work. If the commission is reduced or constrained, the calculation changes.

For users, the case matters only if competition reaches the checkout screen in a way they can see and trust. External purchasing can mean lower prices, direct account management, bundles across platforms, or easier cancellation through a web account. It can also mean more confusing support boundaries. Apple’s EU documentation is blunt on this point: when developers use alternative purchase options, they are responsible for payment and billing issues, taxes, refunds, purchase history, subscription management, and related support that Apple’s in-app purchase system normally handles. That tradeoff is real.

For Apple, the risk is strategic. Services revenue depends partly on the App Store’s commerce layer, and every court or regulator that normalizes external payments weakens Apple’s ability to treat iOS distribution and iOS billing as a tightly coupled package. Apple can still argue privacy, security, fraud prevention, and user experience. But if checkout choice becomes normal, Apple will have to prove the value of its payment system with convenience and trust, not just platform control.

Who is affected now

U.S. developers that sell digital goods or subscriptions are the primary audience. The most exposed categories are games, media subscriptions, education apps, dating apps, creator tools, cloud services, and professional software with existing web billing.

Developers in the EU should not assume the U.S. case automatically changes their obligations. Apple’s EU rules are tied to EU law and Apple’s regional terms, including entitlement, reporting, and fee requirements. The U.S. litigation is its own track.

Consumers do not need to change settings or payment habits today. If an app offers an external purchase route, users should check price, renewal terms, cancellation path, refund policy, and whether support is handled by Apple or the developer. The cheapest button is not always the easiest one to unwind.

What developers should do

First, do not rebuild checkout around a hoped-for legal outcome. The Supreme Court case is live, and 9to5Mac reports that Apple is still trying to pause lower-court proceedings over external-link commissions. Treat U.S. external-link strategy as provisional until the court record settles.

Second, model three scenarios: Apple keeps meaningful commission authority on external links; Apple can charge something, but less or under tighter court supervision; or Apple is sharply constrained and developers get a more direct web-payment path. The operational plan should work under all three.

Third, separate economics from user experience. If web checkout saves only a few points after Apple fees, payment processor fees, taxes, fraud tools, and support staffing, it may not be worth adding friction. If web checkout enables account portability, cross-platform bundles, or materially lower prices, it may be worth preparing.

Fourth, preserve clean records. Any developer using external payment flows should be able to document user consent, pricing disclosures, refund handling, tax collection, subscription status, and transaction reporting. Whether the governing rule comes from Apple, a court, or a regulator, messy records are where margin gains go to die.

Competitive context

Apple is not alone in defending platform fees, but it is more vertically integrated than many rivals. Google has faced its own app-store antitrust fights, including litigation involving Epic, and console platforms still commonly bind distribution and payment tightly. The difference is that iPhone is a general-purpose mobile computing platform with enormous consumer reach, not a dedicated game console. That makes Apple’s control over payment rails more consequential for developers whose entire mobile business depends on iOS access.

The fair competitive argument for Apple is that the App Store did build a trusted, high-conversion marketplace. The fair counterargument is that once iOS distribution becomes practically unavoidable for many businesses, Apple’s ability to tax off-platform transactions can look less like payment processing and more like rent on access.

Bottom line

Today’s development is procedural, but it is useful because it tells developers not to mistake the post-injunction world for settled law. Apple has Supreme Court review on the civil-contempt question. Epic is trying to keep the lower-court commission fight moving. Users may eventually see more web-payment options, but the value of those options will depend on fees, disclosures, support, and whether developers can pass savings through.

The honest read: this is not the end of Apple’s App Store control. It is another pressure point in a longer shift from total platform certainty to negotiated, regional, court-supervised control. Developers should prepare, not overreact. Users should welcome real choice, but read the checkout page before trading Apple-managed convenience for a lower price.

Sources

• Supreme Court of the United States, docket No. 25-1311, Apple Inc. v. Epic Games, Inc.; certiorari granted June 30, 2026, limited to Question 1.
• Supreme Court of the United States, docket No. 25A1213, Apple Inc. v. Epic Games, Inc.; application for stay submitted May 4, 2026 and denied May 6, 2026.
• Apple, petition for a writ of certiorari in Apple Inc. v. Epic Games, Inc., filed May 21, 2026.
• Epic Games, brief in opposition in Apple Inc. v. Epic Games, Inc., filed June 4, 2026.
• Apple Developer Support, “Communication and promotion of offers on the App Store in the EU,” accessed July 13, 2026.
• 9to5Mac, “Epic fights Apple’s request to pause App Store commission proceedings,” published July 13, 2026.