I ran Screen Time for months as a passive counter, never once setting a limit: too many menus, no obvious first move. Once I put the steps in order, the actually-necessary part turned out to be four moves.
iPhone Screen Time lives in the Settings app under Screen Time, and four pieces matter. App Limits set a per-app daily allowance, Downtime closes off a stretch like the night, Always Allowed keeps phone and maps usable through it, and last comes a Screen Time passcode. Skip the passcode and an expired limit lifts with one press of the ignore button, which makes the whole arrangement roughly one more notification.
Open Settings, then Screen Time. Recent versions arrive with it on: switching on App & Website Activity starts the counting. Then the order matters. I fiddled with content restrictions first and left Downtime unset, and one night after nine, the phone I'd resolved to drawer came back out in front of the drawer for another 30 minutes.
| Step | Menu | What to set |
|---|---|---|
| 1 | App & Website Activity | Switch on. Off, everything below sits grayed out |
| 2 | App Limits | Add Limit, pick apps or a category, set the daily time. Customize Days allows per-day amounts |
| 3 | Downtime | Start and end times. Only allowed apps and calls work inside it |
| 4 | Always Allowed | Keep just what Downtime shouldn't touch: phone, messages, maps, alarm |
| 5 | Screen Time passcode | Four digits, required to ignore an expired limit |
Steps one through five take 10 minutes. Do the passcode last, and better, have someone else set it. A passcode I know is barely different from no passcode.
Both stop apps from opening, on different axes. App Limits are an amount; Downtime is a window. Thirty daily short-form minutes is a limit. Nine-to-seven, phone effectively closed, is Downtime. Each alone failed for me: the limit alone got spent in one predawn sitting, and Downtime alone left the daytime untouched.
The combination was the answer: total daily amounts on the short-form and social apps, plus Downtime across the bedtime stretch. Downtime doesn't need to be uniform: open its day-by-day options and weekdays and weekends can differ. I copied weekday rules onto the weekend once, and tore the whole thing down the first Saturday.
Settings all in place, hours unchanged: usually one of these is running. I had all three.
A day the ignore button got pressed isn't a bad day. It's the day the fence showed you where it leaks. Patch the leak, keep the fence.
Where Screen Time stops apps, Sumbi sets a time and puts the phone down. Start a 30-minute dive and the screen can go dark without breaking anything, your remaining breath shrinking only while another app opens. An incoming call is never counted as surfacing, so nights are safe to leave it running.
Try your first 10-minute dive →Ask a spouse or friend to set the passcode and stay ignorant of it yourself: in a house with a kid, the kid can set it. The ignore button moving one step farther away is enough to thin the presses. Truly urgent, you ask: it's distance, not a cage.
Cutting a two-hour app to 30 minutes buys a day-one war with the ignore button. Start about 20 minutes under the current usage and step down weekly. I started at an hour and a half: not at the goal yet, but the ignore button gets measurably less work.
Fence off the whole day and the maintenance alone gets the fences torn down. Pick the single most damaging stretch. Mine is nine to six. I try to get the phone into the drawer then anyway, and with Downtime across those hours, a phone retrieved from the drawer has nothing to show, and goes back in.
Settings are tools. Some days the tool fits the hand, some days it slips. A day the ignore button got pressed was still a day you meant to put the phone down: keep that intent, and the settings can always be re-hung.
Menu names and locations can vary a little by device model and software version. This article is general information, not medical advice.
Sumbi