Delay Lock: Automatic App Blocking After a Delay
Why Daily Screen Time Limits Are Easy to Dismiss
Most screen-time tools work the same way: you set a daily allowance, the allowance runs out, a screen appears, and the screen has a button that makes it go away. One tap later you are back where you were.
The problem is not the allowance. It is that the moment of friction arrives when you are already deep in the app, already absorbed, and the only thing standing between you and the next scroll is a button you have learned to tap without reading.
Delay Lock moves the friction somewhere else. It does not ask you to decide how many minutes a day you deserve. It waits until you have actually been using a blocked app for a while, and then it closes the door for a length you set — long enough to break the loop, and chosen by you rather than imposed.
Automatic App Blocking Without Daily Quotas
Delay Lock is one of the two protections that ask nothing of you. It does not wait for a decision, because the gesture it answers was never one — the app was open before you knew your hand had gone for it. Motion lock is the other of that kind, for the same reflex on the pavement.
The two that do run on a decision are Schedule and the Express widget: the hours you set in advance, and the tap you make in the two seconds you notice. Those carry your will. This one covers the moments where there was none to carry.
How Delay Lock’s Grace Period and Block Duration Work
Two numbers, and nothing else.
The grace period is how long you can use a blocked app before anything happens. Open the app, scroll, read a message — the grace period is running. Close the app before it ends and nothing happens at all.
The block duration is how long the app stays closed once the grace period runs out. During that time, opening the app shows the Upchin block screen instead.
Then the block ends on its own. There is nothing to come back to, nothing to unlock, no notification to dismiss. That is deliberate: a block you have to actively end is a block you will learn to end reflexively, and you are back to tapping a button without reading it.
How to Turn On Delay Lock
- Open Upchin and tap the Delay orb on the home screen.
- Choose which apps the block applies to, in the Selection tab. Delay Lock uses the same app selection as every other protection.
- Pick a rule — Quick friction is the recommended starting point.
- Turn the toggle on.
Upchin asks for Screen Time permission the first time. That permission is what lets the app put a screen in front of another app; without it, nothing can block anything.
Quick Friction and Pomodoro Presets
Two rules come ready to use.
Quick friction gives you sixty seconds of grace, then blocks for thirty. It is the one to start with. A minute is long enough to check a message and get out, and short enough that mindless scrolling hits the wall quickly. Thirty seconds of block is not a punishment — it is a pause that lets the impulse pass.
Pomodoro gives you five minutes, then blocks for twenty-five. It fits a different shape of day: deliberate work sessions rather than ambient interruption.
You can also build your own rules in My rules, with any combination of grace period and block duration. The block duration cannot go below thirty seconds, because a block shorter than that is not a pause, it is a flicker.
Why the Block Sometimes Arrives Later Than You Expect
This is worth understanding before you set a long grace period.
The grace period is measured in clock time, not screen time. Once your usage starts the countdown, the countdown keeps running — whether or not you are still in the app.
With Quick friction this is invisible: sixty seconds pass and you are usually still holding the phone. With Pomodoro it is very visible. Open a blocked app for twenty seconds, put the phone down, and the block will still arrive about five minutes later, while you are doing something else entirely. You can end it immediately with the Back IRL button, but it will have interrupted you.
The timing is also approximate in the other direction. iOS decides when it reports app usage to Upchin, and it does not report continuously. Upchin arms several independent timers so that a block fires even when one of them is not delivered, but the result is a block that arrives around the moment you set, not to the second.
If you want predictable timing, keep the grace period short.
What Delay Lock Is Not
It is not a hard lock. The Back IRL button on the home screen ends a running block in one tap. That is on purpose. Upchin is not trying to take your phone away from you, and a tool that traps you is a tool you will delete. The friction is the point; the imprisonment is not.
It does not block websites by itself. Delay Lock applies to apps. Websites are handled separately, in Web lists.
It cannot distinguish parts of an app. If an app is blocked, it is blocked — there is no way to allow one section and block another.
It does nothing without a selection. If you have not chosen any apps to block, Delay Lock has nothing to act on, and the toggle will tell you so rather than pretending to be on.
Frequently asked questions
Does Delay Lock replace Apple Screen Time?
No. Upchin is built on the same Apple APIs. Screen Time reports how long you spent; Delay Lock puts a screen in the way while you are spending it.
What happens if I close the app during the grace period?
Nothing. No block is triggered. The grace period only matters if you are still using the app when it runs out.
Can I end a block early?
Yes, with the Back IRL button on the home screen. Delay Lock is friction, not a lock you cannot open.
What is the shortest block I can set?
Thirty seconds. Anything shorter is a flicker rather than a pause, so the editor does not allow it.
Does Upchin see which apps I use?
No. Screen Time data stays inside Apple’s privacy container on your device. Upchin draws its charts in there; the app itself cannot read the detail.
Why did a block arrive while I was not using my phone?
The grace period runs in clock time, not screen time. With a long grace period such as Pomodoro’s five minutes, a short visit can trigger a block several minutes later. Keep the grace period short if you want predictable timing.
