If a fixed nighttime boundary fits your routine, you can download 9to9 from the App Store and choose the apps and websites you want quiet from 9 PM to 9 AM.
The word “curfew” is doing some useful work in “digital curfew” — it borrows the structure of a thing adults remember from being teenagers. A curfew is not a suggestion or a goal or a vibe. It is a time, after which certain things stop, enforced by something other than your in-the-moment judgment. That is exactly what makes it a better frame than “use my phone less at night,” which is not a rule at all — it is a wish.
A digital curfew, done well, is one of the more effective things you can do for your evenings. Done badly — vague, overbroad, dependent on nightly discipline — it is another resolution that quietly dissolves by the second week. The difference between the two is almost entirely in the specifics. Here is how to build the kind that survives.
Why adults need a curfew at all
There is a fair objection to address first: is a self-imposed curfew not a little absurd — a grown person giving themselves a bedtime for their phone? The answer is that the curfew was never really a childish idea; it was always a structure for a moment when judgment is weak. The adult version just admits it honestly. The 11 PM version of you is not the best judge of whether the scroll should continue — the curfew is the 2 PM version of you making that call in advance, which is not a lack of trust in yourself but a better use of it.
Make it a boundary, not a wish
The first and most important move: the curfew has to be a fact, not an intention. “Use my phone less at night” fails because it contains no checkable claim — every use is a judgment call, and judgment calls at 11 PM go one direction. “No feeds after 9 PM” is a boundary: at any given moment it is either being kept or it is not, and the question “is it past the time” has a yes-or-no answer that requires no deliberation.
So the curfew needs three specifics, all decidable in advance. The time — one clock hour you can state in a sentence. The scope — which apps and websites count, named explicitly rather than “social media” generally. And the consequence — what actually happens at the boundary, which in the workable versions is the apps simply becoming unavailable rather than you trying to want to stop. A curfew that is only a promise is a curfew you will keep until the first night it is inconvenient.
Keep the useful phone
The second design decision is scope, and the trap to avoid is the total one. The impulse when setting a curfew is to make it cover everything — the whole phone, dead at 9 PM — because it feels more committed. It is also what kills the curfew within days, because a modern phone does too many legitimate jobs at night to be banished entirely: the alarm, the messages from people who might need you, the map, the music, the boarding pass, the two-factor code.
The curfew that survives is selective. Block the feeds — the handful of apps and sites that turn a check into a session — and leave the tools. Phone, Messages, maps, music, reading, health, authentication: the things that are jobs rather than streams. This is not a loophole; it is the difference between a curfew you can live with and one you abandon. You are not trying to go off-grid. You are trying to make the infinite part of the evening finite.
The test for whether something belongs on the blocked list is simple and honest: does it have a bottom? A feed does not — it is designed to never run out. A tool does — the map gets you there, the message gets answered, the song ends. Block the bottomless; keep the finite. That one question sorts the whole phone.
Plan the first twenty minutes, not the whole night
Here is the part almost everyone skips, and it is where curfews actually die: the transition. The feed ends at 9 PM, and then there is a specific, empty, slightly uncomfortable moment — standing in your own home with the evening suddenly open and no idea what fills it. If nothing is waiting in that moment, the curfew feels like deprivation, and deprivation gets renegotiated.
So decide the first move in advance, while you are still in daylight. Not a routine — just the one thing that happens right after the boundary. The shower you have been putting off. The tea. The book already on the pillow. The call to a person. Twenty minutes of a prepared, finite, easy thing is what carries the evening across the gap the feed used to fill; after that, the night tends to find its own shape. The curfew does not need you to plan the whole evening — it needs you to survive the first twenty minutes without reaching for the thing that just closed.
It is also worth staging the thing, not just deciding it. The book should be on the pillow, not on the shelf; the kettle should be where you see it; the person should know you might call. A curfew with a replacement that requires finding is a curfew whose first twenty minutes are spent looking for something to do — which is exactly when the phone gets picked back up.
The curfew is for the evening, not just the sleep
A framing that helps the whole thing hold: the curfew's real product is not better sleep — it is a better last hour. The sleep benefits are real but secondary; what the curfew returns is the evening itself — the hour that was being spent on the feed and is now just yours. People who build the habit tend to describe the change less as “I sleep better” and more as “the night feels like mine again.” That is the truer promise, and the one worth building for.
Automate it — the curfew should not need you
The final and most important property: the curfew has to run on its own. A curfew that requires a nightly act of remembering — starting a focus mode, putting the phone down on purpose, choosing to honor it tonight — has a built-in failure point at exactly the moment it is most needed: the night you are tired, the night you are stressed, the night the feed is especially good. Automation removes the remembering. The boundary just exists.
On the iPhone, Screen Time's Downtime does this natively — a scheduled window where marked apps are restricted while the ones you allow stay available. It is free and worth trying. A dedicated blocker like 9to9 does the same thing with less to manage: the schedule is fixed at 9 PM to 9 AM, the apps you chose go quiet on their own, and there is no list to tend and no window to renegotiate. Whichever instrument you use, the property that matters is the same — the curfew happens whether or not tonight-you feels like having one.
What the first week actually looks like
A short honest preview, because the first nights are where curfews die. Night one feels strange — the feeds go quiet and the evening is suddenly open, and the hand keeps reaching for a phone that no longer answers. That strangeness is not the curfew failing; it is the curfew being noticed. By night three or four the reaching slows, and the quiet starts feeling like space rather than deprivation. The thing to expect is not immediate calm but a week of the evening slowly reappearing — the hour that was always there, now finally yours to use.
Sources: Healthy Sleep Habits (American Academy of Sleep Medicine)
When the schedule does not fit your life
The honest limit of the whole idea: a curfew is a clock, and clocks only work for people whose days run on them. Shift workers, new parents, anyone whose evening does not reliably happen between 9 PM and midnight — a fixed hour is the wrong shape for a life that does not have a fixed evening. The principle still holds — the feeds need an ending — but the instrument has to flex with your schedule rather than repeat a time your life does not keep. For the nine-to-five life, the clock works beautifully; for the irregular one, the boundary has to be attached to the routine rather than the hour.
When a curfew is not enough
An honest caveat, because the curfew is a good tool for a specific problem and a poor one for others. If the late nights are not about the feed — if the phone is just the most convenient thing to be doing while you are awake for reasons that have nothing to do with the phone — then blocking the apps leaves the wakefulness. The curfew addresses the scrolling; it does not address the thing the scrolling was covering. Worth keeping in mind as you build it: if the first quiet evenings reveal that the scroll was filling something, that is information about the real problem, and it deserves its own answer.
The questions that come up
Is 9 PM the right time for everyone? No — it is a sensible default, not a universal prescription. The right curfew is the latest hour that still protects your sleep; for some lives that is earlier, for shift workers it may not be a clock time at all. Pick the hour that fits your real evenings rather than an idealized version of them.
What if I genuinely need a blocked app? Then the curfew needs an escape hatch sized for errands — like 9to9's five-minute Temporary Access — rather than either no exit (which gets the system uninstalled) or an always-open one (which is not a curfew). The real need is a task with an end; the loophole is the thing that has no end.
And what does success actually look like? Not a dramatic change — a quieter one. The evening ends when it is supposed to. The hour between dinner and sleep is yours again. The morning stops carrying the previous night's bill. A curfew you keep is boring in the best way — the boundary, holding, night after night, without you having to hold it.
A final framing worth taking with you: the curfew is not really about the phone. It is about the evening — about the fact that the last hours of the day are yours, and they were being spent on something that did not give them back. The block is the mechanism; the evening is the point. Build the smallest curfew that protects it, and let the nights be quiet again.