The verdict is in, and predictably, both sides are claiming victory. On Friday, Judge Yvonne Gonzalez Rogers issued her ruling in Epic Games v. Apple, and the 185-page decision is far more nuanced than the “Apple wins” or “Epic wins” headlines would have you believe. As a developer who’s shipped apps through the App Store and dealt with Apple’s policies firsthand, I want to cut through the noise and focus on what actually matters for those of us building software.
The Ruling in Brief#
Here’s the TL;DR: Apple won on nine of ten counts. The court found that Apple does not have a monopoly under federal antitrust law. Epic’s claims under the Sherman Act were rejected. The court defined the relevant market as “digital mobile gaming transactions” rather than “iOS app distribution” — a critical distinction that worked in Apple’s favor.
However — and this is the part that matters — Apple lost on one significant count under California’s Unfair Competition Law (UCL). The court issued a permanent injunction ordering Apple to allow developers to include links and buttons in their apps directing users to external payment mechanisms. Apple has 90 days to comply.
In plain terms: developers can now tell users “hey, you can also buy this on our website” and link them there. What developers cannot do is process payments directly inside the app without going through Apple’s in-app purchase system.
What Changes (And What Doesn’t)#
Let’s be precise about what the injunction does and doesn’t change.
What changes: The anti-steering provision — Apple’s rule that prevented developers from even mentioning alternative payment methods — is struck down. This is actually significant. Previously, if your app had a subscription that cost $9.99/month on the App Store, you couldn’t tell users they could subscribe for $7.99/month on your website. You couldn’t even acknowledge that your website existed as a purchase channel. That restriction is now unconstitutional under California law.
What doesn’t change: Apple can still require in-app purchases for digital goods bought within the app. Apple can still charge its 15-30% commission on those in-app purchases. Apple still controls what goes in the App Store and on what terms. The 30% “Apple tax” is not going away.
What’s unclear: How Apple will implement this. The devil is in the details. Will Apple allow a simple “Subscribe on our website” button? Or will they require dense legal disclaimers that make the experience terrible for users? History suggests Apple will comply with the letter of the law while violating its spirit.
The Developer Economics#
Let’s talk about what this means practically. Say you’re an indie developer with a SaaS product that has a mobile component. You charge $10/month. Under the current regime:
- In-app purchase: User pays $10, you receive $7 (after Apple’s 30% cut, or $8.50 if you qualify for the Small Business Program’s 15% rate)
- Website purchase: User pays $10, you receive approximately $9.70 (after payment processor fees)
With the injunction, you can now include a link in your app saying “Subscribe at example.com for $10/month.” A savvy developer might even offer a small discount for web subscriptions: “Subscribe at example.com for $8/month” — still earning more per subscriber while passing savings to the user.
The question is: will users actually follow these links? The friction of leaving the app, opening a browser, entering payment details… it’s real. Apple’s in-app purchase is convenient by design. My guess is that for casual purchases, most users will stay in-app. But for subscriptions and high-value transactions, a meaningful percentage will follow the external link, especially if there’s a price incentive.
For large developers like Spotify, Netflix, and the gaming companies — who already route users to the web for subscriptions — this is a formal blessing of what they’ve been doing informally through workarounds. For smaller developers, it opens a new channel that was previously forbidden.
The Broader Platform Question#
What I find most interesting about the ruling is what it reveals about the court’s view of platform economics. Judge Gonzalez Rogers explicitly acknowledged that Apple earns “supracompetitive profits” from the App Store — profit margins well above what you’d expect in a competitive market. She called Apple’s 30% commission “extraordinarily high.”
But she stopped short of calling it monopolistic, because the court’s market definition included Android. Since users can (in theory) switch to Android, Apple doesn’t have monopoly power in the court’s view.
This is where the ruling feels disconnected from developer reality. Yes, users can switch platforms. But developers can’t simply ignore iOS. If you’re building a consumer mobile app, you need to be on both platforms. Apple’s market share in the US is roughly 55-60%, and its users tend to spend more on apps. Walking away from iOS isn’t a realistic option for most developers.
The ruling essentially says: Apple’s commission is high and arguably unfair, but it’s not illegal because competition exists. That’s a legally sound conclusion, but it leaves developers in a market with two platforms that both charge similar commissions and have similar restrictions. “Competition” that produces identical pricing isn’t exactly what Adam Smith had in mind.
What Happens Next#
Both sides are expected to appeal. Epic has already announced its intention to do so, and Apple will likely appeal the UCL finding. This will end up at the Ninth Circuit, and potentially the Supreme Court.
In the meantime, the 90-day clock on the injunction is ticking. Developers should start planning for how to implement external payment links in their iOS apps. Some things to consider:
- Design the user experience now. How will you present the external payment option? Make it clear, not buried.
- Set up web payment flows if you don’t already have them. Stripe, Paddle, or your payment processor of choice.
- Price strategy: Will you offer a discount for web purchases? The math probably makes sense for subscriptions.
- Watch Apple’s implementation guidelines closely. They will define exactly what’s allowed, and the constraints will matter.
My Take#
This ruling is a step forward, but a modest one. The anti-steering provision was the most developer-hostile aspect of Apple’s policies, and striking it down is genuinely positive. But the core economics of the App Store haven’t changed. The 30% commission stands. Apple’s control over distribution stands. Sideloading remains prohibited on iOS.
I’ve been building software long enough to remember when platform owners didn’t extract 30% of every transaction. The web remains the most open platform we have — no gatekeepers, no commissions, no approval process. Every time I deal with App Store policies, I appreciate the web a little more.
The real pressure on Apple isn’t coming from this ruling. It’s coming from regulatory action in the EU (the Digital Markets Act), South Korea’s new law requiring alternative payment systems, and the general political momentum toward platform regulation. This court case is one front in a much larger battle.
For now, get ready to add that “Subscribe on our website” button. It’s not revolution, but it’s progress.