Skip to content
IdeaScout.
← Back to archive

Streaming "No Spoilers" mode

AI-discovered

Problem

Binge-watchers keep getting shows ruined by the streaming platforms themselves: thumbnails, titles and synopses of later seasons and finales appear on the show page before you've watched them. There is no way to tell Netflix/Prime/Disney+ 'hide everything past the episode I'm on'.

Opportunity

A spoiler-free overlay (browser extension + mobile app) that tracks your watched progress per show and dynamically blurs/hides thumbnails, episode titles and descriptions beyond your progress point across major streaming services.

Market analysis

Free keyword-based spoiler blur extensions already exist in numbers, and at least one open-source project (No-Spoilers-Chrome-Extension) hides episode thumbnails, titles and descriptions on streaming pages. What none of them does is automatic per-show progress tracking — users must configure keywords or click manually, which is exactly the friction this idea removes.

Market · Broad consumer audience of binge-watchers; recurring complaint, but low willingness to pay given free alternatives.

Pricing · Extensions in this space are free or freemium; plausible ceiling is a one-time $3-5 'pro' unlock, subscription unlikely to convert.

score 5/10 by glm-5.1

Pros

  • + Genuinely felt, widely-relatable pain with viral shareability.
  • + Desktop MVP is cheap: DOM overlay + progress tracking is proven feasible.
  • + Auto progress sync is a real differentiator vs keyword-blur tools.

Cons

  • − Free extensions (Hide Spoilers, No More Spoil, SpoilerProtection) already cover the static blur case.
  • − Constant DOM-maintenance treadmill across Netflix, Prime, Disney+ redesigns.
  • − Mobile is the bigger pain point and is unreachable — browser extensions can't run inside native streaming apps.
  • − Any platform could ship this as a native setting and erase the product overnight.

Source

r/SomebodyMakeThis (Reddit)

Open original thread ↗

The hard part is not the blurring — it’s knowing where the viewer actually is. Watched-progress lives inside each platform’s API/UI state, so a cross-service overlay must either scrape player position reliably or ask the user, and both degrade the magic. The realistic wedge is depth over breadth: nail one platform (Netflix) with true auto-progress, treat the rest as best-effort keyword fallback, and market it as “the extension that knows where you stopped watching”. The mobile story is the honest limit: without a native app there is no answer for the person spoiling themselves in the Netflix app on the couch, and that is where most of the pain actually happens.