Rave sues Apple over App Store removal: a reminder that ‘platform competition’ risk is real
A plain-English summary of Rave’s antitrust claims around an App Store removal, and what it means for distribution risk, review resilience, and product roadmaps.
Original reporting (source): Reuters (via KFGO) - “Rave files antitrust lawsuit against Apple over removal of video-sharing app” (May 7, 2026)
What happened
Rave (a co-viewing app that lets users watch and discuss video content together across iOS, Android, Windows, and Mac) says Apple removed it from the App Store in 2025.
Rave is now suing Apple in U.S. federal court, asking for:
- reinstatement to the App Store, and
- “hundreds of millions of dollars” in damages.
Rave’s claim (in plain English)
Rave says Apple’s stated reason for removal was “dishonest or fraudulent activity”, but alleges the real motivation was competitive.
The competitive angle matters because:
- Rave’s model is described as advertising-led, meaning limited or no in-app purchase commission upside for Apple.
- Apple’s SharePlay (introduced in 2021) overlaps with the broad “watch together” use case.
In Rave’s framing, the removal limited consumer choice by making it harder for iOS users to co-view with non-Apple users.
Why this is worth paying attention to (even if you’re not in media)
Most growth teams treat App Store review outcomes as a compliance and operations problem. This story is a reminder it can also be a strategic distribution risk, especially when:
- your product touches a feature area the platform may expand into,
- your monetization model does not align with platform incentives, or
- your app’s core experience depends on capabilities that can be interpreted as “sensitive” (content access, linking, payments, identity, comms).
Whether or not the claims hold up, the impact is the same: a removal is an existential event for an iOS-dependent business.
Practical takeaways for app teams
- Design for review resilience: keep “compliance-friendly” variants of flows (linking, content access, accounts) so you can respond quickly to a rejection or policy shift.
- Treat platform competition as a roadmap input: if a feature starts showing up in OS-level marketing, assume scrutiny rises.
- Have a distribution contingency plan: even a lightweight web fallback (account access, customer support, content browsing) reduces the blast radius.
Tiny win: write a one-page “store risk brief” for your app: top 5 reasons you could be rejected or removed, the owner for each, and the fastest mitigation path (what you can ship in 48 hours).
Read the original: https://kfgo.com/2026/05/07/rave-files-antitrust-lawsuit-against-apple-over-removal-of-video-sharing-app/
Want help with ASO?
If you want this implemented for your app, check out our services - or run your workflow in APPlyzer.