Today might be remembered as a turning point for the mobile development ecosystem. Epic Games deliberately triggered a confrontation with Apple by adding a direct payment option to Fortnite on iOS, bypassing Apple’s 30% commission on in-app purchases. Apple responded within hours by removing Fortnite from the App Store. Epic, clearly prepared, immediately filed a lawsuit and launched a PR campaign called “#FreeFortnite” — complete with a parody of Apple’s famous 1984 ad.
This isn’t a spontaneous dispute. This is a carefully orchestrated legal and public relations strategy, and regardless of where you stand, it has the potential to reshape how all of us build and distribute software.
The 30% Problem#
Apple’s App Store takes a 30% commission on digital purchases. This has been the standard since the App Store launched in 2008, and Google’s Play Store follows the same model. For context, that means if a user buys a $10 in-app item, the developer receives $7 and Apple gets $3.
For twelve years, developers have largely accepted this as the cost of accessing Apple’s platform. But the frustration has been building. Spotify filed an EU antitrust complaint last year. The European Commission opened investigations. The US House Judiciary Committee held hearings on tech platform power just two weeks ago, where Apple’s Tim Cook testified alongside the CEOs of Google, Facebook, and Amazon.
Epic’s move is different because they’re not just complaining — they’re forcing a legal confrontation while simultaneously waging a public campaign. The lawsuit filing is substantive, running to 62 pages and drawing on antitrust precedent. This isn’t a publicity stunt; it’s a legal strategy with serious resources behind it.
Why This Matters Beyond Gaming#
If you’re thinking “I don’t make games, this doesn’t affect me,” think again. Apple’s App Store policies impact every developer who ships on iOS. The 30% commission applies to digital goods and services across the board — subscriptions, digital content, premium features. If your app charges for anything digital, Apple takes its cut.
The restrictions go beyond the commission. Apple’s guidelines prohibit apps from even telling users that they can purchase content elsewhere. You can’t link to your website for purchases. You can’t mention that a web version exists with different pricing. This information asymmetry is what frustrates many developers, myself included. It’s one thing to charge a fee for distribution; it’s another to prevent your customers from knowing about alternatives.
For enterprise and B2B developers, the impact is more nuanced but still real. Apple’s review process introduces unpredictable delays in your release cycle. Their interpretation of guidelines can change without notice, potentially breaking your business model overnight. I’ve worked with teams that spent weeks redesigning features to comply with App Store review feedback, only to see similar features approved in competing apps.
The Possible Outcomes#
Let’s game out the scenarios. If Epic wins — either through the courts or by forcing Apple to negotiate — we could see a reduction in commission rates, the ability to use alternative payment processors, or even the opening of iOS to alternative app stores. Any of these would be significant for the developer ecosystem.
If Apple wins, the status quo continues, but with even more legal precedent backing Apple’s position. This would solidify the current model and potentially embolden similar gatekeeping on other platforms.
The most likely outcome, in my estimation, is somewhere in the middle. Apple has already made small concessions recently — reducing the commission to 15% for subscription renewals after the first year, for instance. A broader reduction or the introduction of a tiered commission structure seems plausible, especially with regulatory pressure mounting from the EU.
What I don’t expect is the complete dismantling of Apple’s walled garden. Apple will argue — correctly, in some respects — that its review process and distribution infrastructure provide real value: security screening, payment processing, global distribution, and consumer trust. The question is whether that value justifies a 30% tax and the restrictions that come with it.
What Developers Should Do Right Now#
Practically speaking, nothing changes immediately. This legal battle will play out over months, possibly years. But there are some prudent steps to consider.
First, if you haven’t already, invest in your web experience. Progressive Web Apps have been improving steadily, and having a strong web fallback reduces your dependency on any single app store. I’ve been advocating for this approach with my teams for years, and the current situation only reinforces that position.
Second, architect your payment systems for flexibility. Abstract your payment processing behind clean interfaces so that if the rules change, you can adapt quickly. Don’t hard-code assumptions about commission rates or payment flows.
Third, pay attention to the regulatory landscape. The EU’s Digital Markets Act is taking shape, and similar legislation is being discussed in the US, Australia, and elsewhere. The rules governing platform businesses are likely to evolve significantly in the coming years.
My Take#
I have mixed feelings about this situation. Apple built an extraordinary platform and invested heavily in the ecosystem that makes iOS development viable. They deserve compensation for that. But 30% feels excessive for what is, at this point, largely automated distribution. And the restrictions on communication between developers and their own customers feel paternalistic at best.
Epic isn’t a scrappy underdog — they’re a multi-billion dollar company making a calculated business move. But the outcome of this fight will disproportionately benefit smaller developers who don’t have the resources to challenge Apple on their own. Sometimes it takes a giant to fight a giant on behalf of everyone else.
Whatever happens, I’m glad this conversation is finally happening in a courtroom rather than just on forums and Twitter threads. The relationship between platforms and the developers who build on them is too important to be governed solely by the platform’s terms of service.
