If a fixed nighttime boundary fits your routine, you can download 9to9 from the App Store and choose the apps and websites you want quiet from 9 PM to 9 AM.
It is a fair question to ask of the whole category, and it deserves an honest answer rather than the marketing one. The marketing answer is yes — install the blocker, watch the screen time drop. The honest answer is more conditional: app blockers can reduce screen time, but whether yours does depends on what the blocker is, what the habit is, and whether the thing underneath the habit gets addressed. The evidence is thinner than the app-store listings suggest, and where it exists it points to a narrower and more interesting benefit than “less phone.”
Let us take the honest version in parts: what blockers demonstrably do, where they fail, and what determines which you get.
What “reduce screen time” should actually mean
A framing worth setting before the evidence, because the question hides an assumption. “Does it reduce screen time” treats the total as the thing to minimize — a number in a dashboard, lower is better. But the harm the research actually points to is not the total; it is the timing and the pattern — the sessions at the wrong hours, the reflexive checks, the scroll that costs the sleep. A blocker that shrinks the night scroll while leaving the day's total similar has succeeded at the thing that matters even if the dashboard barely moves. The question worth asking is not “does it reduce the number” but “does it reduce the sessions that were costing me.”
What the evidence actually shows
There is less research on app blockers specifically than you would expect — most of the research is on screen use and sleep, or on problematic smartphone use generally, rather than on blocking interventions. But the studies that do exist point in a consistent direction.
A randomized trial published in PNAS studied a “self-nudge” app — one sec, which inserts a pause before a distracting app opens — and found a 57% reduction in actual openings of the targeted apps over six weeks. That is friction rather than a hard block, but it is the cleanest experimental result in the category: a small barrier at the moment of opening meaningfully reduces the openings.
Sources: Directing smartphone use through the self-nudge app one sec (PNAS, via PubMed)
The more common finding in the broader literature is associational: problematic smartphone use correlates with bedtime procrastination and later, shorter sleep — which is evidence that the nighttime session is a real mechanism of harm, and therefore that a tool which removes the session is aimed at the right target. The evidence that blocking the session reduces screen time is more intuitive than proven at scale, but the underlying logic — remove the feed during the hours when it expands — is well supported by the research on where the time goes.
Sources: Problematic smartphone use severity and nature is correlated with bedtime procrastination (PMC), Electronic Screen Use and Sleep Duration and Timing in Adults (PMC)
The benefit that is real: the session that never starts
The clearest thing a blocker does is not reduce total screen time — it removes a specific kind of session. The reflexive open, the check that becomes an hour, the scroll that starts because the phone was there: these are the sessions that blocking actually eliminates, because they depend on the feed being one tap away. A block during the vulnerable hours makes the reflex meet a closed door instead of a feed, and the session does not happen.
That is a narrower claim than “reduce screen time” and a more honest one. The blocked hour might be spent on the phone doing other things — a book, a message, a map — or off it entirely; the total may or may not drop dramatically. What reliably drops is the specific thing the blocker was built to stop: the session that was going to steal the hour. For most people, that is the outcome they actually wanted — not a smaller number in a dashboard, but an evening that ended when it should have.
What people report when it works
The pattern in the reports from people for whom blockers do work is consistent enough to be its own kind of evidence. The benefit is almost never described as “I use my phone less.” It is described as the return of a specific thing: the evening that ends, the morning that starts clean, the hour that stopped disappearing. The total screen-time number often drops less than expected — the blocked hour gets spent on other things, some of them still on the phone — but the subjective change is larger than the metric, because what was removed was not time but the worst-timed version of it.
Where blockers fail
Honesty requires the failure modes, and there are several. The bypass is the big one: a block with an easy override is a block that becomes a notification — the Ignore Limit reflex dressed in a different app's clothes. Whether the blocker holds depends on whether the escape hatch is sized for errands or for evenings.
The migration is the second: the feed blocked on the phone moves to the tablet, the laptop, the browser. A block that covers one device and not the habit's other outlets produces a workaround rather than a reduction. And the third is the deepest: the unmet need. If the scroll was serving something — the boredom, the decompression, the hour that is finally yours — blocking it leaves the need intact, and the need finds another outlet. The blocker removes the feed; it does not remove what the feed was for.
The honest test of whether yours is working
A simple diagnostic for whether your blocker is doing the thing: not “did the screen-time number drop” but “did the sessions that cost me stop happening.” If the 11 PM scroll is gone — if the evening ends on time, if the morning does not start in the feed — the blocker is working, whatever the dashboard says. If the total is down but the midnight session is still there, the blocker is reducing the wrong hours. The metric that matters is the specific session you were trying to stop, not the aggregate.
What determines whether it works for you
Three properties decide whether a blocker actually reduces your screen time rather than just relocating it. Selectivity — a block on the apps that become sessions, leaving the tools working, is a block you can live with; a block on the whole phone is one you will route around. Timing — a schedule that covers the vulnerable hours works because it removes the sessions rather than the minutes; an always-on block is a blunt instrument that fails to the first real need. And the escape hatch — a small, deliberate bypass for the genuine errand keeps the system intact; a bypass that is either absent or effortless collapses it.
The fourth factor is the least technical and maybe the most important: whether the hours the block creates have something in them. A blocked feed plus a book is a reduced evening on the phone. A blocked feed plus nothing is a bored person who will find the workaround.
The version that is not about the number
A fair question that surfaces underneath all of this: if the dashboard total does not move much, was it worth it? The answer depends on what the screen time was doing. If the blocked hours were the ones costing the sleep and the mornings, the benefit is real even if the day's total is similar — the harm was never evenly distributed across the hours. A screen-time number that drops ten percent but is all from the midnight stretch is a different outcome than ten percent shaved off the afternoon, and the first is the one worth having. The metric that matters is the night, not the total.
So do they reduce screen time?
The honest summary: yes, when the conditions are right — scheduled, selective, hard to casually bypass, and paired with something for the space they create. The reduction is narrower than the marketing implies: blockers are best at removing the reflexive, high-cost sessions — the night scroll, the morning check — rather than at shrinking total use across the day. Which is, as it happens, the reduction that matters most. The hour at midnight is worth more than the same hour scattered through a Tuesday.
The right expectation is not a smaller screen-time number; it is a different shape of day. The blocker's job is not to make you use your phone less in the abstract — it is to make the specific hours when the phone costs you the most be hours the feed cannot reach. Whether the total drops is almost beside the point. The night ending on time is not.
The tools that fit that description — the scheduled block, the fixed nightly boundary — are the ones where the honest answer is yes. The ones that are easy to dismiss, easy to route around, or aimed at a total rather than a time are the ones where the honest answer is “it depends on whether you will keep letting it work.” Choose the first kind.