Scheduled Blocking
Blocked when it matters.
Open when it doesn't.
Apple's Downtime can schedule a blocked window, but real-world reports show WebView apps breaking, settings resetting, and limits reverting mid-edit. Here's what actually happens, and where a default-blocked approach skips the problem.
Downtime's core idea is sound: pick a window, block everything except what you allow. Set a start and end time in Screen Time, and outside of Phone, Messages, and anything on your Always Allowed list, apps become inaccessible for that window, with a small hourglass icon marking them as locked.
The execution is where it falls apart for a lot of people. Community reports describe WebView-based apps breaking outright, settings quietly resetting, and edits to a limit reverting on their own, all of which turn a scheduling feature into something you have to keep re-checking rather than trust.
What Downtime scheduling can and can't do
It needs a specific toggle to actually enforce anything. Without Block at Downtime turned on, the scheduled window is a dismissible reminder, not a real lock, the same soft-limit pattern that makes App Limits easy to override.
WebView-based apps can break entirely instead of just being restricted. Apps like Amazon, Kindle, and StoryGraph, which render content through a web view rather than native code, have been reported to show only a "Time Limit" screen and stop functioning, rather than simply respecting the schedule.
Settings can reset without warning. Users have reported Screen Time configurations, including Downtime and content restrictions, disappearing after as little as a day, forcing the schedule to be rebuilt from scratch.
App Limits can revert mid-edit. Changing or deleting a limit has been reported to glitch and snap back to the prior configuration, occasionally locking out apps that were never meant to be restricted.
Communication Limits can misfire outside the scheduled window. At least one documented case describes contact restrictions applying even when Downtime wasn't active, despite settings suggesting otherwise.
The four windows people actually try to schedule
Work hours. A block from roughly 9 to 5 on weekdays only, often paired with a separate, more relaxed weekend schedule.
Night and bedtime. This window has the strongest research behind it. A four-week randomized trial found that restricting bedtime phone use reduced sleep latency, increased sleep duration, improved sleep quality, reduced pre-sleep arousal, and improved mood and working memory. Separately, phone use close to bedtime is estimated to delay sleep onset by at least 30 minutes, and pediatric sleep guidance suggests a lockout starting a full 60 minutes before a child's target sleep time.
Morning. A shorter window right after waking, aimed at the automatic reach-for-phone habit rather than a fixed block of hours.
Weekends. Often the loosest schedule, or intentionally the same as weekdays for people whose distraction doesn't actually let up on Saturday.
| Tool | Scheduling model | Watch out for |
|---|---|---|
| Screen Time Downtime | One daily schedule, or separate weekday/weekend schedules | WebView app breakage, settings resets, limit reverts |
| Freedom | Recurring daily or weekly sessions, Locked Mode | Requires configuring separate blocklists per context |
| Opal | Recurring sessions | Free tier limited to three recurring sessions |
| AppBlock | Context-aware Profiles by time, location, or Wi-Fi | The most setup of the group to configure fully |
| Fella | Blocked every day by default, no schedule to build | Built for one daily unlock, not scheduled exceptions |
Where Fella fits
No schedule means nothing to reset or revert. Chosen apps stay blocked every day, which automatically covers work hours, evenings, mornings, and weekends without four separate windows to configure and maintain.
Still reachable for something real. One 5-minute emergency unlock a day covers a genuine need without reopening the door for the rest of whatever window you're in.
Scheduled blocking FAQ
Go to Settings, then Screen Time, then Downtime, and set a start and end time. Only Phone, Messages, and apps you add to Always Allowed remain accessible during that window, and Block at Downtime needs to be on for it to actually enforce anything.
Documented issues include WebView-based apps like Amazon, Kindle, and StoryGraph breaking entirely instead of just being restricted, App Limits reverting when edited, Screen Time settings disappearing after a day, and Communication Limits sometimes restricting contacts outside the scheduled window.
Not by default. Without the Block at Downtime toggle enabled, Downtime shows a soft reminder that can be dismissed with a tap, similar to the Ignore Limit option on App Limits.
Yes. Downtime supports a single daily schedule or separate schedules for weekdays and weekends, and third-party tools like Freedom and AppBlock support recurring schedules and context-based profiles for the same purpose.
Yes. A four-week randomized trial found that restricting bedtime phone use reduced sleep latency, increased sleep duration, improved sleep quality, and improved mood and working memory. Phone use near bedtime is separately estimated to delay sleep onset by at least 30 minutes.
It depends on how complex your schedule needs to be. Freedom and Opal support recurring sessions, AppBlock supports context-aware profiles triggered by time, location, or Wi-Fi, and Fella skips scheduling entirely by keeping chosen apps blocked every day by default.
Because for many people, the distraction isn't confined to one clean window. Fella keeps chosen apps blocked all day, covering work hours, evenings, mornings, and weekends automatically, with one 5-minute emergency unlock instead of a schedule that has to be configured and maintained.