App blockers rarely fail by getting uninstalled. They go quiet and you stop noticing. What the research found, and what I keep getting wrong as the developer.
If your app blocker stopped working, the odds are you never uninstalled it. It is still on your phone. You widened the list, or you left the tag in a drawer, or you started using the manual toggle instead of walking to the kitchen, and none of that felt like quitting at the time. That is the normal way these tools end, and it is mine too: I wrote Lock and I still go weeks where it does nothing for me. So the useful question is not why app blockers fail. It is why they go quiet, because the answer is different and the fix is smaller than you would guess.
The failure is passive, not dramatic
Researchers have a name for this. A quasi-experimental study published in JMIR Formative Research followed 252 passive users of a screen time app called Detox: people who had kept the app installed but had switched its nudges off, or set the usage thresholds so high that nothing ever triggered. The app was still there. It was doing nothing.
The researchers prompted half of them to reconfigure their settings. 46% (63 of 138) accepted. Among those who did, the daily proportion who actually got nudged went from 29.7% before the intervention to 58.5% after, an increase of 36.3 percentage points attributable to the prompt (P<.001). One nudge, and a third of the population came back.
Then the part that matters more. Engagement started declining after roughly two weeks, and within a month the group that had been re-engaged had converged with the group that had not.
Read that twice, because it reframes everything. A successful intervention, statistically clean, bought about a month. Not a defect in the study. That is the shape of the thing. Whatever you do this week to restart your blocker, plan on doing it again about a month from now.
The most common reason people stop is not weakness
A survey of 273 higher education students asked who was using digital self-control tools and why the others had stopped. 51.65% (141 people) were not currently using any of the assessed features. Among the 175 who said they actively suffered from distraction, 31.50% (86 people) were using nothing at all. So the gap is not ignorance. They know, and they still are not running anything.
The reasons for quitting were coded into 355 responses. The largest category by a wide margin, 130 of them, was that the tool was no longer needed once the stressful period ended. The example the authors quote is three words long: “Because exams ended.”
The other categories are the ones you would expect, and they are much smaller:
| Reason for stopping | Responses |
|---|---|
| No longer needed, the stressful period ended | 130 |
| Found a workaround (tablet, another device) | 17 |
| Too restrictive, blocked things they needed | 15 |
| Negative emotions, including guilt | 15 |
So the modal story is not a person tapping through a warning screen. It is a person who set the thing up for a deadline, met the deadline, and never reinstated it. Which is completely rational, and also exactly why the ordinary weeks in between are a mess.
My blocker has never let me down during a deadline. It lets me down in the quiet weeks, when nothing is on fire and nobody is waiting on me.
Building it is bad training for using it
Being the developer is close to the worst possible preparation for being a user.
I open Lock many times a day and almost never as a person trying to focus. I am checking whether the grace delay cancels correctly, reproducing something in the app picker, confirming the session timeout fires when it should. Testing a lock is the exact inverse of living under one: you unlock constantly, on purpose, and you get very good at not minding. The gesture stops meaning anything, which is the one thing the gesture has to do.
The features I lean on hardest as a developer are the ones I should touch least as a user. Manual mode exists so you can try Lock without owning a tag, and so nobody is stranded if a tag goes missing. It is also, honestly, the fastest available way to make the app stop mattering. I built the escape hatch, so of course I know exactly where it is.
None of this makes Lock worse than the alternatives. It makes me a bad witness for it, which is why this article is built on other people’s data and not on mine. I wrote about that problem in more detail: my own numbers would be a sample of one, measured by someone with an interest in the result.
Three things that survived
Here is what has actually held, across restarts.
The tag lives where a routine already goes. Not “somewhere inconvenient”. Inconvenient and never visited means never tapped, and never tapped means the app is off. The tag needs to sit somewhere my body already arrives at a predictable time: the coffee machine, the kitchen counter, the desk I sit down at anyway. Friction is only useful if it is on a path you already walk. The setup guide goes through the placements in detail.
Fewer apps than feels right. Two or three, never twelve. A wide block feels serious on day one and resented by Wednesday, and “too restrictive” is a real category in that student survey for a reason. A narrow block that survives a month beats a total block that survives a weekend.
Treating lapses as the base rate, not as a verdict. This is the one that changed most. The month-long fade in the Detox study happened to people who had just successfully re-engaged. If that is what a good outcome looks like in a controlled study, then my own gaps are not evidence that friction does not work. Friction works when it is present. Most of the work is putting it back, and putting it back is not a confession, it is maintenance.
What to do this week
- Open your blocker and find the date of the last real session. In Lock that is the streak and the session history on the stats screen. If the last one is older than two weeks, you are a passive user, and that is the entire diagnosis. Nothing is broken.
- Reconfigure once, tighter and smaller. In the Detox study the people who came back set consecutive usage thresholds about 21.5% shorter than before, not longer. Restarting worked when the rule got stricter, not gentler.
- Cut the blocked list down. If you currently block eight apps and use none of it, block two apps and use it.
- Move the tag onto a path you already walk. If you have to remember to go there, it will not happen.
- Put the next restart in your calendar now, about a month out. You already know what the data says. Stop being surprised by it.
I am not going to end this by telling you I solved it. I ship the app, I lapse, I come back. What actually changed is that I stopped reading the lapse as proof the approach is wrong. The tag has never once failed to lock my phone. It only fails when it is in a drawer, and that is a logistics problem, not a character one.
If something in Lock is what put your tag in the drawer, I would genuinely like to know which part. The support page has the address.