Why did the blocker stop working after a week? Because a blocker is a rule with a door in it, and the door has to exist. Every bypass you use teaches your hand a shorter route. Within about two weeks the block stops being a wall and becomes a step, which you take without reading. Nothing broke. The design has that ending built in.
Here is the sequence, because almost everyone runs it the same way.
Day one to four: it works
The first few days after setting a limit are genuinely good. You reach for the app, you get stopped, you feel briefly annoyed and then slightly pleased with yourself. Screen time drops. You tell someone about it.
This part is real, and it is also the part that misleads you. What is working right now is not the wall. It is the novelty and the fresh intention behind it. Both have a half-life.
Day five to ten: the first bypass
Something legitimate comes up. You need to message someone on Instagram. You need to look up a restaurant. You tap Ignore Limit, or type the passcode, and you get in, and it is fine.
The important part is not that you bypassed it. It is that you now know exactly how many taps that took. Three. And that it was not painful.
Day ten to twenty: the bypass becomes the interface
Now the block screen is not a stop. It is a loading screen. Your thumb learns the position of the button. You are tapping through before your eyes have focused on the words.
People describe this precisely and often. "I tap ignore limit before I even register that it appeared." "The block screen is just part of opening Instagram now." "My hand does it." That is motor learning working exactly as designed, applied to the wrong thing.
Day twenty onward: one of three endings
You escalate. Harder blocker, longer delay, a passcode you do not know. This buys another two weeks and raises the stakes of the eventual failure. The escalation ending is where people end up giving a partner the code and then having a fight about it, which we wrote about in when your partner holds the Screen Time passcode.
You delete it. Usually at night, usually irritated. Then you feel bad about deleting it, which is its own small tax.
You leave it installed and stop seeing it. The most common ending. The app is still there, still reporting, still technically enabled. It has no effect on anything. Six months later you notice it in your settings.
Why this is structural
Three properties make the ending predictable.
A block has to have an exit. Apple requires it. Common sense requires it. You will one day need that app for something real. So the exit exists, and anything that exists on your phone gets used until it is automatic.
The block fires at the worst possible moment. It appears when you are already reaching, which is exactly when your capacity for reconsideration is lowest. A rule set by calm-you at 2pm is being enforced against tired-you at 11:40pm, and tired-you has the phone.
Blocking treats it as a supply problem. The premise is that you scroll because the app is available. But availability is not why. Look at what people actually describe when they explain their own scrolling: they were wired and could not sleep, or they had one hard thing to start and could not start it, or nothing at all happened and the hand just went. Remove the supply and the state that produced the reach is still there. It finds another app. That is why people who block Instagram end up on the mobile browser, and why blocking the browser sends them to YouTube.
What actually addresses it
If the problem is that the open was never a decision, then the fix is not a stronger no. It is a moment where a decision becomes possible.
That is a different category of tool. Instead of refusing entry, it interrupts the sequence for a few seconds and then lets you in. You can read the full argument in what a scroll-breaker is and the app blocker that doesn't block.
reCalm does this with one breath. A shield appears over the app you chose, you breathe once while a shape expands and contracts, the app opens. It will not stop you. It will make the open conscious, and a share of conscious opens end with the phone going down.
Because it never says no, there is nothing to tap through and nothing to defeat, so the two-week decay does not have anything to work on.
If you still want a blocker
Some situations want a wall, and we would rather say so.
Use a hard blocker when the app is doing damage now rather than draining you slowly, when the cost of getting in is genuinely unacceptable, or when you are in the first weeks of stopping something and need the friction while other things settle. Brick is the strongest version, because the unlock is a physical tag you can leave in another room. Opal is the better scheduler if your problem is shape of day rather than reflex.
And you can run both. A limit for the shape of the day, a pause for the reach.
If what you actually wanted was to keep other people out of an app rather than yourself, that is a different and much easier problem, and iPhone solves it natively. The split is set out in app lock vs app blocker.
Frequently Asked Questions
Is it a discipline problem?
No. The same pattern shows up in people with obvious discipline in every other part of their life. It is a design outcome: a rule with an exit, enforced at the moment of lowest resistance, against a behaviour that was never deliberate.
Would a longer delay fix it?
It buys time and it raises irritation. Long delays get solved by opening the app earlier, "pre-unlocking" before you actually want it, which quietly makes things worse.
What about giving the passcode to someone else?
It works while the relationship can carry it. It routinely turns a private problem into a shared argument. Worth reading the specific failure in when your partner holds the Screen Time passcode.
Do I have to uninstall my blocker to try a pause?
No. They sit at different points. The limit governs the day, the pause governs the reach.