Why blocking apps fail you after a week

Day one with a hard blocker feels great. X is a grey page, YouTube is a grey page, and you get more done before lunch than you did all last week. By day eight you may well have found the way round it. It's a common story, and not one people tell proudly.

It isn't a character flaw. It's what happens when a tool is wrong often enough that switching it off starts to look like good sense.

The list is right on day one, and wrong by Thursday

A blocklist gets written in a calm moment, for a day that never quite arrives. Then a real day turns up. A client sends a YouTube link. The ad review needs Facebook's ads pages. The person you're waiting on only answers on WhatsApp.

The blocker can't tell any of that apart from the drift it was built to stop, so it says no to all of it. Every wrong "no" teaches you two things: the rule is sometimes wrong, and the rule can be switched off.

Every false alarm pays for the workaround

A block that fires on real work costs you the minute it takes to get past it, and a little trust. Pay that three or four times and the blocker gets turned off "just for this morning". Then just for today.

That's the week-one cliff. The tool didn't fail because you're weak. It failed because it was wrong often enough to be ignored, and a tool you ignore is worse than none: it still feels like protection.

The harder the lock, the bigger the exit

Hard locks answer this by taking the switch away. A block that survives a restart, a session you can't end early, a list you can't edit until the timer runs out. Some people need exactly that, and for them it's the right tool. The comparisons say which apps do it well.

For a lot of us, though, a lock just moves the drift somewhere else: to the phone, to a second browser, to the app the list forgot. You didn't decide to stop. The tool decided for you, and when it lets go at five o'clock, so do you.

What a ten-second nudge does instead

A block decides for you. A nudge asks you. In SqwarkSelf it goes like this. You've started a watch on "marketing and ads". You open X. Only that window goes dark, under a veil, with one line on it: This isn't marketing and ads. Your words, handed back to you. A ring counts down ten seconds.

• Back to work (in Safari, Chrome, Arc, Brave or Edge, Close tab): out at once, and you land back in what you were doing.
• This is work: it's let through for the rest of the watch, and your call is logged.
• Do nothing: after ten seconds the app is hidden, or the browser switches to a tab you were working in. Nothing is killed, and nothing is closed unless you pressed the button.

Ten seconds is long enough to notice what your hand just did, and short enough not to feel like a punishment.

Why being wrong costs less

When a nudge is wrong, you press This is work and carry on. That app, or that site, stays out of the way until the watch ends. On sites that can go either way, like YouTube, it's just that page, so one tutorial doesn't open up all of YouTube. You don't open settings and you don't switch anything off.

A false alarm that costs one click doesn't make you want the off switch. And because the click is logged, the end of the day shows how often you said "this is work". You're the only one who knows whether it was.

When a nudge isn't enough

If you'll click past anything, ten seconds of a parrot won't hold you, and you want a lock. SqwarkSelf doesn't have one. It's also Mac only: if your drift lives on your phone, a Mac app can't see it. Both are good reasons to pick something else, and those pages say what.