Apple says Epic lawsuit shouldn’t reshape App Store rules for all developers
Apple is contesting a court ruling in its ongoing lawsuit with Epic Games regarding App Store fees. The company argues that any injunction resulting from Epic's claims should not apply to all developers. Apple is also challenging a contempt order related to its compliance with a previous injunction requiring it to allow alternative payment links in apps.
- ▪Apple is asking the U.S. Supreme Court to review a lower court ruling that could impact all developers on the App Store.
- ▪The Ninth Circuit ruled that Apple must allow developers to include links to alternative payment options, which Apple has complied with but charged fees on those transactions.
- ▪Epic Games criticized Apple's latest legal maneuver as an attempt to delay the case and maintain its fee structure.
TechCrunch files mainly under tech. We currently carry 772 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | TechCrunch |
| Canonical URL | https://techcrunch.com/2026/05/22/apple-says-epic-lawsuit-shouldnt-reshape-app-store-rules-for-all-developers/ |
| Publication time | Fri, 22 May 2026 16:27:57 +0000 |
| Retrieval time | 2026-05-22T16:32:02.589Z |
| Last seen | 2026-05-22T16:44:49.818Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | PaxTsxeqYHEy |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
In Apple’s seemingly never-ending lawsuit with Fortnite maker Epic Games over App Store commissions, the iPhone maker is once again fighting a court’s ruling. Its latest tactic? Saying that Epic Games’ beef with Apple over its fee structure shouldn’t lead to an injunction that applies to all developers that publish on the U.S. App Store, including other tech giants like Microsoft and Spotify, which weren’t a part of this particular litigation. “…Epic never brought a class action and never attempted to show that enjoining Apple’s conduct against all other developers—like Microsoft or Spotify, who have nothing to do with Epic—was somehow necessary to provide relief to Epic,” reads Apple’s new petition, which asks the U.S. Supreme Court to review the lower court ruling.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at TechCrunch.
Discussion
0 commentsMore from TechCrunch
