Worth building.
At the searched framing: a clean, locked-down app blocker whose core blocking contract never changes under the user's feet — no surprise UI overhauls, no feature degradation post-payment, no hidden limit tightening
Counted from 2,762 real App Store reviews across 13 apps
Markdown — pastes cleanly into Claude, Notion, anywhere.
Two principles that win it.
Stable blocking contract
Core blocking rules — schedules, hard-mode locks, friction challenges — are versioned and user-owned; no update may silently remove or alter a block the user configured, ever.
Honest, predictable limits
What is free is free permanently and what requires payment is priced transparently upfront; no dark-pattern gating that forces payment mid-session or after onboarding investment.
37% of reviews run negative.
2,762 reviews · 13 apps · vs a 9,161-app baseline.
Content runs 3.63× the baseline.
11% of complaints, against a 3% norm across 9,161 apps.
50% land at 1–2 — a switching driver, not a wish.
The demand side, counted
People type the wound into Google before they ever write a review:
Google Suggest (US) shows presence and shape, not volume; the trend is relative search interest over 12 months — direction, not size. A second axis beside the verdict, which weighs the review evidence above.
“Ever since the 4.0 update, this app has been incredibly buggy for me. Blocks not engaging, blocks not expiring, random parental controls I never asked for added to my device. I just finally deleted it and canceled my subscription. I've never wanted the functionality of an app more, yet been relieved I was deleting it.”
Every app owns part of it. None owns the gap.
Content runs 3.63× the norm — and no one has closed it.
At or below the norm — table stakes, not where you win.
The wedge, scoped to what you ship next.
- Rule versioning: every blocking rule is stored with a user-readable config snapshot; updates cannot silently modify it
- Temporary override that respects user intent: a full-day pause (not just a 15-minute window) accessible in two taps, with optional accountability confirmation
- Transparent free tier: define exactly which features are permanently free before first-launch, never move them behind a paywall post-onboarding
- Reliable hard-mode: math or delay challenge that persists correctly across app restarts, confirmed with a session-start checksum
- Countdown timer always visible while a block is active — no launch-required check
- Minimal onboarding: no unskippable quizzes on reinstall for existing accounts; returning users land directly in their schedule view
- Don't redesign the core blocking UI post-launch without a user-controlled rollback path — Opal's exact failure mode
- Don't gamify the blocking flow with scores, achievements, or streaks that encourage opening the app — the product's job is to keep users out of apps
- Don't gate scheduling or hard-mode behind a paywall after a user has configured rules on the free tier
- Don't build an accountability-partner social layer in v1 — it adds support complexity (BlockerX's wound) before the core blocking contract is proven stable
- Don't use a VPN-based blocking architecture without surfacing performance impact clearly — silent slowdowns are a top billing-refund trigger
- Don't launch with more than two pricing tiers; the 7–10 tier structures across competitors create confusion that reads as manipulation
Each claim maps to a verbatim review.
“Someone didn’t test enough!! New update broke key functionality, out of nowhere all adult websites were being blocked on my phone when they never used to be… took me days to understand it was a hidden setting in this stupid app. Now I’m considering deleting the app, I never configured that… Don’t break user trust”
“I thought this would be a great way to decrease my screen time as well as build strength. I answered all the questions TWO times through to move on and then it told me I had to pay. It says it’s for unlimited access but there’s no way to X it out. Please let me know if there’s any way to get past the paying screen.”
“Not user friendly, confusing, impossible to end a rule for a day. For example, I block apps during my work day. If it’s a holiday or vacation and I want access to my blocked apps, only option is up to 15 minutes. Can’t turn off for the day. Will wait for the next update before uninstalling but the app sucks now.”
“I cannot use google or safari even if they are set as unblocked !!! If I try to set the specific website I need to access to unblock, they do not come up. Also, if I try to unlock an app for one of the 3 unlocks I have set, it changes to a screen that doesn’t allow me to unlock. Wasting my app unlocks!!!”
Assumptions most likely to sink it.
Opal defectors will actively switch rather than tolerate or return to Opal when it patches v4.0
Intercept Opal-review authors (App Store replies, Reddit r/nosurf, X) with a landing page describing the stable-contract pitch; measure whether they click through and, crucially, whether any pay for early access — not a waitlist signup
If fewer than a meaningful share convert to paid early access (money changes hands), the defection window is noise and the acquisition thesis must shift to organic/SEO rather than the Opal exodus
Apple's Screen Time API is stable and permissive enough to deliver a reliable hard-mode block that cannot be trivially bypassed
Build the smallest possible hard-mode prototype (delay challenge + schedule lock) and test bypass vectors manually; check Apple's ShieldConfiguration and FamilyControls entitlement changelog for deprecation signals
If the API permits easy bypass (as AppBlock's receipts suggest — 'plug into charger and apps are unblocked'), the core promise is technically unfulfillable on iOS without MDM, and the product narrative must shift to friction-as-commitment rather than true blocking
Users who are angry at billing will pay a clean, honest subscription rather than abandoning paid blockers entirely
Once a minimal version ships, measure free-to-paid conversion rate against a clearly disclosed paywall shown before any onboarding investment; a strong result is real payment, not survey intent
If conversion is low despite transparent pricing, the billing anger reflects category fatigue with subscriptions generally — the model shifts toward a one-time purchase or donation tier
The wishlist theme (ratio 1.63, mean_star 3.04, 11 of 13 apps) signals feature demand that can differentiate v2, not just parity noise
After shipping v1, tag support requests and in-app feedback by wishlist sub-theme (scheduling granularity, group management, ADHD-friendly one-tap flows); rank by frequency among paying users only
If wishlist requests are diffuse and low-volume among payers, treat them as long-tail polish rather than a roadmap driver and hold scope to the stability core
If Opal ships a v4.1 rollback within 60 days that collapses its negative rate back below 40% and paying defectors publicly return, the exodus window closes and the verdict flips from Build to Validate on acquisition — the demand exists but the unlocked cohort disappears.
content complaints run at 3.63× the corpus norm across 11 of 13 apps; limits complaints at 3.51× across 9 of 13; ux at 3.01× across 7 of 13 — all three are category-wide wounds, not one app's problem. Opal at 82,117 ratings and 67% negative is the dominant defection signal. billing complaints appear in all 13 apps at 33% of negative reviews (mean_star 2.01 — a switching driver). The category's overall negative rate is 1,018 of 2,762 reviews; baseline_neg_pct is 55% — this niche sits above norm in content and limits specifically. Paid models demonstrably exist: IAP tiers up to $99.99 (Opal), $89.99 (AppBlock), $59.99 (PushUp Time, Refocus) at meaningful rating counts.
Acquisition cost against a brand-aware incumbent is unobserved; Opal's v4.0 defection window may be temporary if they ship a rollback; ScreenZen and Refocus's low negative rates are promising but based on smaller captured samples and may not hold at scale
Did this sharpen your decision on App Blocker?
See where the opening is in your category.
You just walked the same market, gap, and build analysis you’d get for your own idea.
Run my category report2,762 reviews · 13 apps · cross-checked against a 9,161-app baseline · verbatim quotes · Jul 2026