Friction gate for doomscrolling on X/Reddit/HN
A browser extension that forces a short cognitive-load task (math, typed intention) before opening known doomscroll sites, for people who already tried quitting cold.
People describe the problem, but nothing on file shows them paying to solve it. That gap is the thing to test first.Evaluated Aug 11, 2026 · thresholds published at /methodology
Supporting evidence2
A user explicitly describes wanting a tool to enforce cognitive breaks before accessing distracting content, and describes doing math as a self-imposed friction mechanism.
A separate user quit a major platform entirely because the feed served unrequested, repetitive content, showing willingness to abandon incumbents rather than tolerate the problem.
Falsifying evidence4
Only 2 signals support this cluster, both from a single source (HackerNews), which is not representative of mainstream social media users likely to need this most.
The incumbents named (Reddit, Instagram) control the feed algorithm directly and could ship native 'take a break' or reduced-repetition features themselves, cutting off the wedge.
Free, trivial alternatives already exist (site blockers, app timers, browser extensions like StayFocusd) and the signals do not mention any dissatisfaction with those alternatives, only with the platforms.
No revenue data exists for any cited product or signal, so there is no evidence anyone will pay for a friction gate rather than using free blocking tools or simply logging off, as one user did.
Most likely cause of death
The founder builds a friction-gate extension, gets a wave of interest from people who self-identify as doomscrollers, and then watches retention collapse within weeks because users disable the extension the first time they're mildly inconvenienced (uninstalling is one click) and because free blockers already solve 80% of the problem for zero cost. Defensibility would need to come from something incumbents can't easily copy — e.g., cross-platform intention-tracking or social accountability — not from the friction mechanic itself, which any browser extension or the platforms' own settings menu can replicate.
Demand ladder
A complaint is not a customer. Weighted ×1 / ×3 / ×8 / ×15.
Verified revenue: none on file for this problem yet. That is an absence of records, not proof nobody is earning here.
Momentum
Is this problem getting louder or quieter?
Saturation
How many people are already on it. Most sites hide this.
Problem evidence
Who feels this, how often, and why what they use today does not fix it.
- Who feels it
- Technically literate adults who read Hacker News, X, Reddit and news sites reflexively on a laptop, have already noticed the habit degrading something they care about (deep work, math practice, sleep), and have already tried quitting by willpower or by deleting an account. Evidence is limited to this population — all five signals come from Hacker News.
- How often
- Daily, in short involuntary bursts. The trigger point is the reflex tab-open between tasks; the pain is reported as accumulated ('I spend too much time') rather than as a single acute incident, which matters because there is no invoice-shaped moment that forces a purchase.
- Why current fixes fail
- The two fixes people describe both fail at the same moment: the moment of reflex. Hard blockers (site blockers, app timers) are binary — they either block a site the user genuinely needs for work several times a day, so the user disables them by mid-morning, or they are set loosely enough to be irrelevant. Quitting a platform outright works but costs the whole platform: one signal reports leaving Instagram entirely because the feed was unusable, i.e. the fix is amputation, not moderation. Neither addresses the specific gap the doomscroll signal names: wanting a deliberate pause between reflex and feed while keeping access. There is no evidence in this block that anyone is dissatisfied enough with the free blockers to switch — counter-evidence explicitly notes the complaints target the platforms, not the tools.
At least one user explicitly wants a cognitive-break mechanism before reaching distracting sites, framed exactly as this idea: doomscrolling X/Reddit/HN while losing the ability to do real math.
The desire to reduce feed consumption without leaving the platform appears repeatedly: users object to repetitive, algorithmically injected content they did not ask for, and want it filtered rather than the platform abandoned.
Some users solve the problem by full withdrawal instead of by tooling — one stopped using Instagram outright, another population is described as buying single-purpose devices to escape smartphones. Withdrawal is a free substitute for any product in this category.
There is exactly one datapoint of money changing hands anywhere near this problem: a developer built a $5 app for their own phone addiction. It is a one-time $5 price set by a self-treating builder, not a validated market price, and no sales figures are given.
Free, adjacent tools are already in these users' vocabulary — Scrolless Feed Blocker is named by a user, and site blockers/app timers such as StayFocusd are on file as trivial free alternatives. Nobody in this block complains about them.
The whole cluster rests on three signals from a single source (Hacker News), with a weighted demand score of 7 and no 30-day movement. This is not evidence of a market; it is evidence that a handful of engineers described the feeling out loud.
The wedge is structurally exposed: Reddit, Instagram and X own the feed and can ship native 'take a break', reduced-repetition or screen-time settings, and browser vendors can ship site-level limits, in either case removing the reason to install anything.
No signal in this block shows anyone paying for friction specifically — no subscription, no trial, no price discussion beyond the $5 app.
Who buys it
The person who feels the pain and the person who signs are rarely the same.
Who buys it is part of membershipThe buyer, the budget it comes out of, and what these people already pay for.Product concept and MVP
Two versions: the one you deliver by hand first, and the one you build.
Product concept and MVP is part of membershipThe concierge version, the buildable version, and the features deliberately left out.Competitors and alternatives
Including the free workaround people use today, which is usually the real competitor.
Competitors and alternatives is part of membershipDirect products, indirect ones, the workarounds, and where the gap actually is.Pricing model
modelledA proposal, not an observation. Benchmarks come from the data; the ladder is ours.
Pricing model is part of membershipA tier ladder with the reasoning behind each price point.Revenue scenarios
modelledArithmetic on the assumptions listed underneath. Change an assumption and the number changes.
Revenue scenarios is part of membershipBase, upside and aggressive cases with every input written out.Market size
modelledReachable customers, not a top-down industry figure.
Market size is part of membershipHow many buyers exist, what they spend, and how many you could realistically reach.Go to market
Named places, not channel categories. These signals came from somewhere.
Go to market is part of membershipWhere the first ten customers come from, then the first hundred.Roadmap
Each version ships something a user can use. No infrastructure-only phases.
Roadmap is part of membershipVersion by version, with what belongs in each.Pivot paths
Where this goes if the first version does not land — and the number that says it did not.
Pivot paths is part of membershipAdjacent directions, and the measurable trigger for taking one.Risks and kill criteria
The thresholds at which the honest move is to stop. Written before you are attached to it.
Risks and kill criteria is part of membershipRanked risks, and the numeric conditions under which to walk away.Validation plan
Seven days that cost nothing but time and can kill the idea before you build.
Validation plan is part of membershipA day-by-day plan and the interview questions that do not lead the witness.Sources and freshness
Every reference opens the original post. This is the part you should check first.
How sure are we, per claim
Where the data is thin, we say so instead of rounding up.
- demand
- Low
- payment
- No data
- market size
- Low
- competitor gap
- Low
13 references from 2 signals · evaluation written Aug 11, 2026.
Related opportunities
Nearest by what the problem actually is, not by category label.
Bot-traffic triage dashboard for indie site operators using Cloudflare
A lightweight log-analysis layer that classifies bot vs human traffic and flags scrapers Cloudflare's default rules miss, for solo site owners.
Skill-sync CLI for Claude Code / Codex agent configs across repos
A CLI and background sync daemon that keeps Claude Code/Codex agent skills, prompts, and settings identical across a developer's repos, flagging drift before it causes side effects.
Escalation-to-human triage add-on for SMB SaaS AI support widgets
A drop-in escalation layer that SMB software vendors plug into their AI chatbot so frustrated users can reach a real human, sold to the vendor not the end user.
Eleven more sections behind this one
Who signs the cheque, what the space already charges, the seven-day validation plan, and the thresholds at which you should stop. Three ideas are open in full so you can judge the depth before paying.
0 people have looked at this · 0 turned it into a spec · 0 say they're building it