An app blocker for work should run in timed sessions rather than all day. Block for ninety minutes at a time, cover the browser versions as well as the apps, and schedule the blocks in advance so starting one is not a decision you have to make while avoiding work.
The reason an app blocker for work usually fails is that people set it up wrong on day one. They block everything, all day, and by Wednesday they have turned the whole thing off because they needed one blocked thing for one legitimate reason.
A block you disable is worse than no block, because now you have also learned that disabling it is easy.
Set up an app blocker for work in sessions, not all day
Block in defined stretches with a defined end. Ninety minutes is a good default. The apps go, you work, the apps come back.
Three reasons this holds better than an all day block.
- It has an end you can see. Anything indefinite feels like deprivation and gets resented. Ninety minutes feels survivable because it is.
- It survives legitimate need. Someone really does message you about something real sometimes. If your only option is switching off a day long block, you switch it off.
- It matches how work actually happens. You do not need protection from 9 to 5. You need it for the two or three stretches where the hard thinking happens.
What to block, including the bit people miss
The obvious list is social media. Block it. But the things that actually eat a knowledge worker's day are often the ones that feel like work.
- Email. Not during a session. Email is other people's priorities arriving in real time, and answering it feels productive while reliably preventing the work that matters.
- Team chat. The worst one, because it is socially costly to be unavailable. Block it for ninety minutes, tell people you do that, and let the expectation adjust.
- News. Feels like being informed. Functions identically to a feed.
- The browser versions. Blocking the app and then using the website is how this quietly fails. See how to block websites on iPhone.
- Your work laptop, separately. An app blocker on your phone does nothing about the same sites on the machine in front of you. Phone blocking is half the job if you work at a computer.
Schedule the sessions in advance
This is the part that makes the difference and the part everyone skips.
If starting a focus session is a decision you make in the moment, you will make it on good days and not on bad ones. But bad days are precisely when you needed it, so your blocker will be running exactly when it was least necessary.
Put two sessions in the calendar as repeating events. 09:30 and 14:00, ninety minutes each. Decided on Sunday, not decided at 09:29 while you are already avoiding something.
There is a second benefit to scheduling that has nothing to do with discipline. A block in the calendar is visible to other people, which quietly does the hard social work for you. Nobody argues with a calendar entry, and you stop having to decide each time whether being unreachable is acceptable today. The question has already been answered by the version of you who set it up, which is the whole principle this page rests on.
How long to block for
| Work type | Session | Why |
|---|---|---|
| Writing, coding, analysis | 90 minutes | Long enough to get past the uncomfortable start |
| Admin and email | 25 minutes | Short bursts suit shallow work, and the dread is the problem rather than the focus |
| Meetings | Meeting length | Mostly so you are actually present |
| Studying for something | 50 minutes | Retrieval is tiring and quality drops before the time does |
A note on the popular claim that it takes 23 minutes and 15 seconds to refocus after an interruption. That figure gets quoted constantly and the underlying research is thinner than the precision suggests. Switching tasks does cost you something real, and you do not need a specific number to know that forty interruptions is worse than six. More on that in the 23 minute claim.
What the evidence actually supports
Be careful with productivity claims here, including mine. No trial has shown that app blockers increase work output, and anyone telling you otherwise is selling something.
What has been tested is the wellbeing side. A 2025 randomised controlled trial in BMC Medicine took 111 students averaging 276 minutes of phone use a day and had 58 of them hold under two hours a day for three weeks. Against the control they improved on stress, wellbeing, depressive symptoms and sleep quality.1
Stress and sleep are not nothing for working life. But that is a different claim from output, and it was measured on students rather than on knowledge workers.
The other finding worth carrying over: usage returned towards baseline once the limit ended.1 A blocker you use for a sprint week gives you a sprint week.
What it cannot fix
It will not make you want to do the work. Blocking apps removes one escape route, and if you are avoiding something for reasons unrelated to your phone you will find another route, usually within the hour.
If you are reaching for your phone constantly during a specific task, that is worth treating as information about the task rather than about your discipline. Unclear next step, unclear ownership and quiet dread all produce the same behaviour, and no blocker touches any of them.
Where SETL fits
SETL Sessions is the daytime half of SETL: pick the apps, pick the length, and ending early takes a deliberate press and hold rather than a tap. Bedtime blocking runs automatically on top of it, which matters more for work than it sounds, since most bad working days start with a bad night. It is iPhone only, so if your problem is your laptop, it is only part of the answer.