Let's talk about Apple and Epic again. You've probably seen the headlines: Apple's been dragged back to court, forced to propose Apple's cost-based fees for purchases made *outside* the App Store. They're talking 5% to 15%, depending on the app. Epic, naturally, says it should be 0%. The immediate question is clear: why should Apple take a cut for transactions that don't even happen on their payment rails? This legal sparring highlights a core problem: how platform owners like Apple justify taking a slice of your revenue, particularly when it comes to these controversial cost-based fees.
The 'Service' You Didn't Ask For
Mainstream news calls this Apple being "forced to cut fees." Technically, yes. They were found in civil contempt in April 2025 for trying to slap a 27% fee on external transactions – a clear violation of a 2021 court order. While the Supreme Court has agreed to review that contempt finding, a lower court is proceeding with determining a "reasonable" commission. Apple recently sought a temporary stay from the Supreme Court to pause these lower-court proceedings, but the request for a longer delay was denied, compelling Apple to submit its fee proposal. As a result, Apple is on the hook.
Forget the percentage for a moment. The real fight is the *principle*. The court demands a "cost-based" fee. That's the key. Apple must prove what it *actually costs* them to handle a transaction that happens entirely off-platform, via a web link. This is where the concept of Apple's cost-based fees becomes critical.
If a user clicks a link in your app, goes to your website, and buys something there, Apple's justification for a 5% or 15% cut is unclear.
The Phantom Costs Apple Might Invent for Their Cost-Based Fees
This is where the financial implications become clear. Many developers are already calling it out: Apple is trying to "fabricate outlandish new notions of cost" to justify *any* commission. This assessment is accurate, especially concerning Apple's cost-based fees.
Apple's potential arguments for these costs are limited. They might claim 'App Store Discovery,' arguing your app wouldn't exist without their store, thus deserving a cut of everything. However, that's a revenue-share argument, not a cost for *external* payments. This distinction is crucial when evaluating the legitimacy of Apple's cost-based fees.
Similarly, 'Security Reviews' are a standard platform cost, performed regardless of whether you link to your own payment system. It's not a cost *per external transaction*. The same applies to 'SDKs and APIs' – these are platform costs, not transaction-specific for something happening *off* the platform. Finally, the 'Brand Value' argument – essentially, "You're on an iPhone, so we deserve money" – is the ultimate vendor lock-in play, with zero relevance to the actual cost of processing an external payment.
Many developers contend that for a transaction entirely on your website, using your own payment processor (like Stripe or PayPal), Apple's direct, incremental cost is effectively zero. They aren't hosting, processing, handling fraud, or providing support for that purchase. This makes the concept of significant Apple's cost-based fees for such transactions highly questionable. The industry is watching closely to see how Apple attempts to justify these specific cost-based fees.
This isn't about Apple providing a service. It's about them trying to maintain control and extract rent from an ecosystem they built, even when you step outside their tightly controlled platform.
What This 'Tax' Actually Costs You
Here are the numbers. Say your app pulls in $1,000,000 in external purchases annually. This isn't just for Epic Games; for many growing developers, $1,000,000 in external purchases is a significant threshold.
To illustrate the impact of these proposed Apple's cost-based fees, let's compare Apple's proposals against Epic's push for 0%.
| Cost Factor | Apple's Proposed 15% Fee (Worst Case) | Apple's Proposed 5% Fee (Best Case) | Epic's Proposed 0% Fee (Developer's Goal) |
|---|---|---|---|
| External Purchase Revenue | $1,000,000 | $1,000,000 | $1,000,000 |
| Apple's Commission | $150,000 | $50,000 | $0 |
| Your Payment Processor Fees (e.g., a hypothetical 3%) | $30,000 | $30,000 | $30,000 |
| Total Cost to Developer | $180,000 | $80,000 | $30,000 |
| Net Revenue to Developer | $820,000 | $920,000 | $970,000 |
| Lost Revenue (vs. 0% scenario) | $150,000 | $50,000 | $0 |
Losing $150,000 isn't trivial; that's the equivalent of funding a senior engineer or a significant marketing campaign. It's pure profit Apple tries to skim off the top for a service they don't provide. Even at 5%, that's $50,000 you hand over for nothing. These are significant costs imposed by Apple's cost-based fees.
This isn't about *their* payment processing costs. It's about the cost of *your* freedom to choose.
The Verdict: Push for Zero
The court demanding a "cost-based" fee is a key moment. It forces Apple to move past vague claims of "value" and actually put a number on what they do for transactions they don't directly handle. For external web purchases, that number should be next to nothing. This directly challenges the premise of significant Apple's cost-based fees.
Many developers and users express frustration with Apple's monopoly tactics and constant delays. They want Apple to lose its restrictive platform control.
Any commission above 0% for purchases made via web link-outs is a tax, not a service fee. It's an attempt to maintain a revenue stream with no basis in actual cost.
What You Should Do
For CTOs, engineering managers, and founders, this isn't just Epic's fight. It directly impacts your budget, your margins, and your ability to control your own business. The immediate imperative is to relentlessly push for 0% when it comes to Apple's cost-based fees for external transactions. Support groups fighting for truly open platforms, because this legal precedent will impact every platform you build on. This isn't just about Apple; it sets a standard for how all major platform holders might attempt to extract revenue from off-platform activities.
Beyond advocacy, you must scrutinize every 'cost.' When a platform vendor tries to justify a fee for something they don't directly provide, demand a detailed, auditable breakdown of their *actual* costs. Don't let them hide behind 'ecosystem value' — that's code for 'we want more money.' Understanding the true cost of doing business on these platforms is paramount.
Ultimately, the most powerful move is to build direct relationships. Move your customer relationships and transactions off-platform as much as possible. This strategy not only bypasses unnecessary fees but also gives you greater control over your data, customer experience, and revenue streams. That's how you control your revenue, not Apple's.
Apple's proposal is an attempt to preserve a revenue model that lacks justification for off-platform transactions. The courts are forcing them to show their math. When they do, I'm betting it won't add up. The future of fair platform economics hinges on the outcome of these discussions around Apple's cost-based fees.
