Newest signal 483h oldHow the evidence is collected →

← All ideas
Narrow the wedge· lowMembers only

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.

Re-researched — no candidate cleared the gates. The verdict below predates candidate-relative attribution. When this idea was re-examined, every candidate generated for it was blocked:
  • the deterministic verdict came out negative — the evidence argued against building it (VERDICT_KILL)
  • the outcome the product promises is not controlled by the product (CONTROLLABILITY_GATE_FAILED)
  • not enough evidence dimensions were resolved to decide either way (COVERAGE_BELOW_MINIMUM)
Thresholds are published at /methodology.

The broad concept is not supported by the evidence. A narrower direction is on file: Accountability pair / partner-held gateEvaluated Aug 14, 2026 · thresholds published at /methodology

consumerb2cWeekend MVPdifficulty 2/5

Turn this into a build spec

One Universal Core, then the exact file layout your platform expects — CLAUDE.md, .cursor/rules, a Lovable knowledge base, a Bolt prompt under its 400-word ceiling. Evidence travels with it.

32 credits · every platform format after it is 5

Reading an open idea needs nothing. Generating a spec from it calls a model and costs real money, so it needs an account and credits — the cost is shown before you spend anything.

Building this?

Tell everyone else. It shows on this page and on the idea cards, and it collects in your dashboard. Ship it and add the link — we fetch it and re-check it weekly.

Sign in to tell others you're building this.

36
Signal momentum

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 evidence3

  • The founder's stated cause of death is retention collapse because users disable the extension when inconvenienced, and uninstalling is one click. This is not a falsifiable risk you can design around—it's the central mechanism failing. If the friction gate works (blocks access), users remove it; if it doesn't work (easy to bypass), it has no effect.

  • The signal set shows people articulating the problem (S-1869, S-2256) but contains zero evidence of anyone paying for or sustaining use of a solution. The one paid app mentioned (S-7) is presented as a personal build with no retention data, and Instagram itself is listed as a product in this space (P-1320) despite being the thing users want to escape.

  • Free browser extensions and native platform settings (Screen Time, Digital Wellbeing) already offer blocking, friction, and time limits at zero cost. The stated cause of death acknowledges this directly: 'free blockers already solve 80% of the problem for zero cost,' leaving no clear wedge for a paid product without the cross-platform or social features the evidence never mentions anyone wanting.

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.

Complaint 1 ×1
Would pay 1 ×3
Already paying 0 ×8
Verified revenue 0 ×15

Counted from clustered complaint signals. No candidate-relative commercial check was applied, so no revenue is attributed to this idea.

Verified revenue: not established for this idea. No record ties a revenue figure to a product selling what this would sell.

Momentum

Is this problem getting louder or quieter?

not enough history

Saturation

How many people are already on it. Most sites hide this.

20 views·0 specs·0 building
01

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.

medium confidence

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.

medium confidence

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.

medium confidence

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.

low confidence

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.

high confidence

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.

high confidence

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.

medium confidence

No signal in this block shows anyone paying for friction specifically — no subscription, no trial, no price discussion beyond the $5 app.

high confidenceno source on file — treat as opinion
02

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.
03

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.
04

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.
05

Pricing model

modelled

A 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.
06

Revenue scenarios

modelled

Arithmetic 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.
07

Market size

modelled

Reachable 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.
08

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.
09

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.
10

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.
11

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.
12

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.
13

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

9 references from 2 signals · evaluation written Aug 11, 2026.

Related opportunities

Nearest by what the problem actually is, not by category label.

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.

20 people have looked at this · 0 turned it into a spec · 0 say they're building it