August 13, 2020. Apple pulls Fortnite from the App Store.
I keep coming back to this day, because on the surface it looks like a stunt, and if you stop reading before the technical part, that’s exactly how you’d remember it.
That same day, Epic Games remotely triggered a hotfix called “Project Liberty” inside Fortnite: code quietly embedded in an earlier, Apple-approved update and switched on server-side, without a new App Review, that unlocked a direct payment option routing around Apple’s in-app payment system. Within hours Apple removed Fortnite from the App Store, and Google pulled it from Play the same day. Epic was already staged: a video called “Nineteen Eighty-Fortnite” and an antitrust complaint dropped almost simultaneously.
It looked like a publicity stunt. It wasn’t, not really. It was an engineering probe: Epic built code whose only job was to expose exactly which technical rule enforces Apple’s 30% commission: the in-app payment mandate, the App Review rules, and the entitlements that decide what an app is allowed to do. The whole case turned on one question, and it’s the question I want you to hold onto through everything that follows: is that architecture user protection, or market control.
What the court actually decided
It isn’t what the headlines said.
In September 2021, after a three-week bench trial before Judge Yvonne Gonzalez Rogers in the Northern District of California, Epic lost nearly every antitrust claim. The court found Apple hadn’t been proven a monopolist in the relevant market. But Epic won one narrower claim, under California’s Unfair Competition Law: Apple’s anti-steering rules, which barred developers from even linking, inside their own apps, to outside payment options, were an unfair business practice. The court issued an injunction barring Apple from blocking apps from including links or buttons to payment methods outside its own system. The Ninth Circuit affirmed both rulings in April 2023 (it reversed only on an unrelated attorney-fees issue), and the U.S. Supreme Court declined to hear the appeal in January 2024.
That alone tells me the case wasn’t decided on “is Apple greedy.” It was decided on what a specific technical rule actually does: security feature, or economic gate.
The artifact: the compliance mechanism became the evidence
The injunction took effect in January 2024. Apple built its own compliance layer around it: external links were now allowed, but Apple charged a commission (27% on any transaction completed within seven days of a link-out) and added deterrent warning screens before a user left the app (compliance with the letter of an order, sprinting flat-out from its spirit). Epic went back to court arguing the mechanism gutted the injunction.
In April 2025, Judge Gonzalez Rogers ruled that Apple’s compliance scheme violated the injunction’s letter and spirit, a finding the Ninth Circuit later affirmed in full. More than that: she found that an Apple vice president, Alex Roman, had given false testimony under oath, contradicted by internal engineering documents produced at the hearing, and referred the matter for a criminal contempt investigation on that basis (the emails, unlike the vice president, apparently hadn’t been coached). The court ordered Apple to stop collecting the commission on off-app purchases and remove the warning screens, effective immediately. Apple asked the Ninth Circuit to pause the order; the request was denied.
The fight over what that ruling means isn’t finished. In December 2025, the Ninth Circuit upheld the contempt finding but said an outright ban on any fee went too far: it ruled Apple may charge a narrower fee, limited to costs “genuinely and reasonably necessary” for handling external links, and sent that number back to the district court to set. In June 2026, the U.S. Supreme Court agreed to hear Apple’s appeal on a narrow question: whether a court can hold a company in contempt for violating an injunction’s “spirit” rather than its literal text. Argument is expected in the term opening that October, which means the very finding this piece is built on is, as of this writing, still being tested at the highest level.
Sit with what actually decided this round, because it’s the whole point of this piece. It wasn’t a marketing statement or an executive’s press quote. It was an internal engineering email thread showing what Apple’s engineers had actually designed, and how that contradicted what an executive swore to in open court. The artifact in this case isn’t “Fortnite” or “the 30% fee.” It’s the engineering record of the enforcement mechanism itself: the internal thread showing Apple’s engineering team deliberately built a fee and a warning screen designed to preserve the economic outcome the injunction had banned.
Why this needs a software expert witness, not a generalist
Here’s where I’ve watched even sharp people miss this. A lawyer reading Apple’s App Store Review Guidelines can quote them. A generalist engineer can explain, in general terms, how StoreKit and receipt validation work. Neither answers the question that decides a case like this: whether a specific technical rule (a link block, a warning-screen design, a conditional fee) was built to protect users, or built to keep the old economics in a new wrapper.
A court-appointed software expert doesn’t start with an opinion about “monopoly.” They start by defining a narrow technical question: what does the code actually do at the decision point, how does the system detect an outbound payment link, and what happens next. Then comes a list of materials: code diffs, App Review logs, internal engineering correspondence, financial telemetry on transactions routed through those links, followed by a repeatable method and a conclusion with its limits stated: what the evidence shows, and what it can’t show without guessing at intent.
That’s what survives cross-examination. An expert who can point to exactly where the engineering record contradicts the sworn testimony, which is what happened here, is an expert the court believes.
This is where a source code expert witness earns its place — a document that explains the finding rather than just presenting it.
Why Israeli counsel and tech GCs should care
This is the part I want Israeli counsel and tech GCs to sit with. Israeli companies building apps, payment platforms, or business models that depend on the App Store and Play Store face the same issue from the other direction: entitlement rules, review rules, and enforcement mechanisms set by the platforms shape their business model. If an Israeli developer argues a platform rule suppresses competition, or if an Israeli platform builds its own access rules, the evidence that decides it won’t be a marketing deck. It will be code, logs, and internal engineering correspondence.
The practical move: don’t wait for a dispute to preserve the engineering history. Document why a technical rule was built the way it was, and keep the correspondence that explains it, because as this case shows, a court knows how to read between the lines.
The takeaway
Epic v. Apple will keep getting cited as “the App Store war.” That’s the easy headline. The harder lesson, the one I keep coming back to, is that both rounds of the case decided so far (the original judgment and the contempt ruling) turned on what the code actually did and what the engineers actually wrote to each other, not on how the companies described themselves. That’s not a question a lawyer or a generalist engineer answers convincingly. It’s a court-grade software expert’s job.
The above is general information only and does not constitute legal advice. Case facts are drawn from the sources cited.