A lock has to be beaten, and a threshold only has to be crossed. That is the entire difference, and it decides whether you are still using the tool in a month. Put a passcode in front of an app and you have created a small opponent, which you will defeat, and the defeat will be remembered. Put ten seconds in front of it and there is nothing to win, so there is no loss to carry.
Not block, interrupt
The distinction sounds like marketing until you watch what each one does over six weeks.
A block makes a decision in advance, on your behalf, taken from a moment when you felt strong. It then holds that position against a version of you it has never met: later, tired, and specifically motivated. That confrontation has exactly one ending and it is documented in why your app blocker stopped working.
An interruption makes no decision at all. It puts something in the path and then gets out of the way. You can always keep going, and the fact that you can always keep going is not a weakness in the design, it is the load-bearing part of it.
Why the passcode always loses
Every passcode scheme runs the same arc.
First week, it works, because the friction is novel and the motivation is fresh. Second week, you know the code, and entering it takes four seconds. Third week, entering it is as automatic as the reach itself, and the friction has been absorbed entirely.
Then comes the escalation. A longer code, a randomiser, a partner who holds it. Each step buys another fortnight and raises the stakes of the eventual failure, and the version where somebody else holds it fails in a more expensive and more social way, described in we gave each other the Screen Time passcode.
The end state is always the same: you get in anyway, and now you also feel like someone who breaks their own rules. The net effect is negative. You would have been better off with nothing, which is the uncomfortable finding in strict mode made it worse.
What ten seconds does that four seconds does not
It is not about the duration. A four second passcode and a ten second breath are both trivial amounts of time.
The difference is what the time is made of. A passcode is a task with a right answer, so it recruits the part of you that solves things, and solving it feels like winning. The attention never leaves the goal. You are, the whole time, a person getting past an obstacle.
A breath has no right answer and cannot be failed. There is nothing to solve, so the solving part does not switch on, and the attention has somewhere to be that is not the screen. What that actually accomplishes, stated without the wellness overclaim, is in what one breath actually does: it breaks the motion into two parts, and the second part is a decision rather than a continuation.
You often decide the same thing. Fine. Opening the app on purpose and finding yourself in it are different events, and only one of them produces the accounting problem in the hours you cannot account for.
Where a real lock is still the right tool
Locking is not always wrong. It is wrong for this.
If the goal is keeping other people out of an app, a lock is correct, native, and immediate, and the two cases are separated properly in app lock versus app blocker. Face ID on a banking app is a lock doing exactly its job.
The failure is applying a keep-others-out mechanism to a keep-yourself-out problem, where you necessarily hold the key. A lock you hold the key to is not a lock. It is a delay with a grudge attached.
What this costs on iOS
Being honest about the price: putting anything in front of an app on iPhone requires Screen Time authorisation, which is a real permission with a genuinely alarming-looking prompt. Some people will decline it and that is a reasonable thing to do.
What it buys is that the interruption is attached to the app rather than to a clock, so it never fires at a wrong moment, which matters more than it sounds and is argued in interrupting only while you scroll. The native limits that ship with iOS use the same permission and then put a dismiss button on the result, which is where they lose, as set out in how to limit apps on iPhone.
That trade, one real permission for an interruption that only exists at the right apps at the right moment, is the whole of reCalm. One breath opens the shield. Nothing else is asked, counted or kept.
Frequently Asked Questions
Does a breath actually stop me opening the app?
No, and it is not trying to. It converts an automatic motion into a decision. The decision frequently goes the same way, and the difference shows up in whether you can account for the hour afterwards.
Why not just use a passcode?
Because you hold it. Within three weeks entering it is as automatic as the reach, and every escalation after that raises the cost of a failure you will still have.
Can I skip the breath?
Yes. A threshold you cannot cross is a lock, and locks in this position create an opponent. You can always keep going is the design, not a loophole in it.
Is this the same as iOS app limits?
Same permission, different ending. The native limit hands you a dismiss button, which trains the tap that makes it useless, examined in you tap Ignore Limit before you read it.