Their day

A phone bedtime that runs itself, every night

A wind-down time for school nights, a later one for weekends, a morning end, and an optional homework block in the afternoon. At the set time, games, video and social apps go to sleep; calls, the alarm and anything you mark as always allowed stay awake. The schedule is stored on the child’s phone, so it runs with no signal and no Wi-Fi, and the child can see tonight’s time on their own screen before it arrives. Nothing is scheduled until you set it.

Android · Either build · Permission: Accessibility service · Runs offline · Visible on their phone

The bedtime schedule in the parent app with school nights 21:30 to 07:00, weekends 22:30 to 08:00 and a homework block from 16:30 to 17:30

What does the phone do when the bedtime arrives?

Games, video and social apps go to sleep; the phone itself stays on.

Twelve minutes before the time you set, a banner appears on the child’s phone: “Phone sleeps in 12 minutes · alarm and calls still work.” At the time itself, every app that is not on the always-allowed list stops opening. Tapping one shows a plain screen inside the app with the time it wakes up again, the name of the parent who set the schedule, and a Close button. The home screen is still there. The lock screen is still there. Nothing is wiped, hidden or shut down.

In the Okafor house the school-night time is 21:30 and the morning end is 07:00, so at 21:30 Amara’s TikTok, YouTube, Roblox and WhatsApp stop opening and at 07:00 they start again. The clock on the phone, the alarm she set for 06:50 and incoming calls from Priya all behave exactly as they did at 21:29. If she has left a video playing, it pauses rather than cutting off mid-sentence; the pause screen explains why. That is the whole of what happens. It is deliberately dull.

Will the bedtime still run if the phone has no signal?

Yes. The schedule lives on the phone, not on our servers.

When you save a schedule in the parent app or the panel, it is sent to the child’s phone and stored there. From then on the phone keeps the schedule itself, using its own clock, and needs nothing from us to run it. A night at Grandma Ngozi’s with no Wi-Fi, a tent in a field, a flat in a basement with one bar of signal: the 21:30 wind-down happens at 21:30 regardless, because the thing enforcing it is the app on the phone, not a message from the internet.

The one thing that does need a connection is a change. If you move bedtime to 22:00 for a sleepover, the new time reaches the phone on its next check-in, which is usually within minutes when the phone is online and whenever it next connects if it is not. The parent app shows whether tonight’s schedule has reached the phone, with the time it was confirmed, so you are never guessing which version is running. Until a change is confirmed, the old schedule runs, which is the safe failure.

What still works during wind-down?

Calls in and out, the alarm, the clock, the dialler, and every always-allowed app.

A bedtime that locks a child out of calling home is a bedtime a parent switches off after the first late train, so the list of what stays awake is not negotiable and not editable downwards. Incoming calls ring. Outgoing calls connect. The alarm fires. The clock, the torch, the camera and emergency calling work. Then there is the always-allowed list, which is yours to extend: a music app for falling asleep to, an audiobook app, the school’s homework app for the one night a term when the essay is late.

What does not stay awake is anything you have not put on that list. Messaging apps are the ones parents hesitate over. Our advice is to let them sleep: a WhatsApp group at 23:40 is the thing most parents installed a bedtime for. If a friend needs to reach your child urgently overnight, a phone call rings through, and a child who knows that is less anxious about the group than a parent expects.

What is the homework block, and what does it pause?

A second, shorter wind-down in the afternoon, with its own always-allowed list.

The homework block is optional and off by default. Switch it on and it behaves like a bedtime that lasts an hour: in the Okafor schedule it runs 16:30 to 17:30 on school days, and during that hour the same apps that sleep at night sleep again. The difference is its own always-allowed list, which is where Chrome, the calculator and whatever the school uses for assignments go, so the block pauses the distractions and not the work.

Two honest limits. The block cannot tell whether homework is being done; it only removes the apps that compete with it. And an hour starting at 16:30 assumes a child who is home by 16:30, which is not every day. Swim Club evenings end after six, so Priya set the block for Monday to Thursday and left Friday and swim nights out. A homework block that fires while the child is in a pool does nothing useful and teaches them that the schedule does not understand their week.

Can the school-night and weekend times be different?

Yes. Two times for sleep, two for waking, and Friday counts as a weekend night.

A schedule has a school-night pair and a weekend pair. School nights are Sunday to Thursday, because what matters is the morning after; weekend nights are Friday and Saturday. Amara’s weekend wind-down is 22:30 with an 08:00 end, an hour later at each end than the school-night times. Noah’s, at nine, is 20:30 and 21:15, with the morning end the same seven days a week because he is awake at 06:30 whatever day it is.

There is no third pair for holidays. Most parents move the school-night times later for the summer and put them back the week before term, which takes a minute each way and gives the child a visible marker that the holiday has started. Editing a time is the same screen whether you do it in the app on your phone or in the panel on a laptop, and the child’s phone shows the new time the same afternoon.

Will my child know the bedtime is coming?

Yes. Tonight’s time is on their home screen, and a banner counts down the last twelve minutes.

The child app’s home screen shows tonight’s wind-down time all day, next to the screen time ring, so there is no ambush at 21:30. The transparency screen lists the full schedule: both pairs of times, the homework block if it is on, and the always-allowed list, with the name of the parent who set each one. When you change anything, the child’s phone updates the same afternoon. A child who can read the schedule can plan the evening around it, which is the point of making it visible rather than something that just happens to the phone.

The banner is also the moment to put the phone on charge outside the bedroom, if that is the house rule; the app cannot enforce where a phone sleeps, only what it will open, and the two rules work best together.

Noah, at nine, mostly uses the banner as a timer: twelve minutes means one more level, and he knows it. Amara reads the schedule once in September and then ignores it, because at thirteen the schedule is boring, and a boring schedule is one that is working.

What if they are out late, or it is a special night?

You push tonight’s wind-down back from your phone; the child cannot do it from theirs.

From the parent app, tonight’s time can be moved later with a couple of taps, and the change applies to tonight only; tomorrow goes back to the schedule. The child’s wind-down screen has no “Ask for more time” button of its own, which is a difference from the screen time budget and a deliberate one. Bedtime is the rule families told us they did not want negotiated from the sofa at 21:28. If the child wants a later night, they ask you in person, you decide, and the phone follows.

If a child is out at 21:30, nothing dramatic happens: the apps go to sleep where they are, calls and maps still work, and they can ring you from the bus. A parent who knows the evening will run late moves the time before leaving the house. A parent who forgets gets a phone call from a child who can still make one, which is the design working as intended.

How does the bedtime fit with the screen time budget?

The budget counts minutes; the bedtime sets hours. Whichever is stricter wins at that moment.

The two features are independent and both can be on. The screen time budget says how many minutes a day; the bedtime says which hours of the day are available at all. If Amara has 40 minutes of budget left at 21:30, the bedtime wins and the apps sleep anyway. If she has used her budget by 19:00, the budget wins and the apps are paused before bedtime arrives. Neither can override the other; they simply stack.

Many families run bedtime alone for younger children, because a nine-year-old with a 20:30 wind-down and a school day in between does not have enough free hours to need a minute budget as well. The reverse is also common: a sixteen-year-old with no budget and a 23:00 wind-down they agreed to. Start with the one that solves the problem you have, and add the other only if a problem remains.

The wind-down screen, as the child sees it

Either buildAccessibility serviceChild app

The twelve-minute banner is the first thing the child sees, and it says three things: how long is left, that the alarm and calls still work, and who set the time. That last line matters more than it looks. A screen that says “set by Priya” is a rule from a parent; a screen that says nothing is a phone malfunctioning, and children treat the two very differently. After the time, opening a sleeping app shows the same wording with the wake-up time added, and a Close button. There is no fake error, no spinner, no pretence that the app has broken.

The Accessibility service is the Android permission that lets the app draw this screen over another app. Without it the schedule still exists and the banner still appears, but sleeping apps open anyway, because there is nothing to stop them. Device health flags the permission by name when it is missing, and the child’s setup checklist explains the alarming dialog Android shows when it is granted. Grant it together on pairing day and the bedtime works from the first night you set one.

  • Twelve minutes, every night. The warning is long enough to finish a round or send a last message and short enough not to become background noise.
  • The same wording at the homework block. “Homework time until 17:30 · set by Priya”, with the always-allowed apps named so the child knows what is open.
  • Wake-up is silent. At 07:00 the apps simply open again. There is no morning notification, because nobody needs a phone to announce that it is working.
The child app’s wind-down banner reading Phone sleeps in 12 minutes, alarm and calls still work

The week view: seven days of routine on one screen

Either buildParent app and panel

The Routines screen draws the week as a grid, one row per day, with a bar for each block: the overnight wind-down, the homework block, and any scheduled app blocks you have set elsewhere. It exists so you can see the shape of a week at a glance rather than reading times off four separate fields. A homework block on Monday to Thursday and none on Friday shows as four short bars and a gap. A Saturday wind-down an hour later than Friday’s shows as a bar that starts further right.

The grid is also where overlaps become obvious. If the Swim Club finishes at 18:10 and the homework block runs to 17:30, the gap is visible. If an app block on a schedule for Discord runs during school hours and the homework block starts at 16:30, you can see that Discord has exactly one open hour on a school day, and decide whether that is what you meant. The view changes nothing by itself; it shows what the rules you have set add up to, per child.

  • One child at a time. Switch between Amara and Noah with the chips at the top; the grid redraws with that child’s schedule.
  • Tap a bar to edit it. The editor opens with that block selected, so moving Thursday’s homework block is two taps and a time.
  • The child sees a plainer version. Their transparency screen lists the same blocks as text, times and names, without the grid.
A weekly grid of routines in the parent app with bars for each day showing the wind-down and homework blocks
The schedule, row by row

Every field on the bedtime screen, what it does and what we would set it to.

The schedule has fewer settings than parents expect. Each one is listed here with the Okafor values, so you can picture the screen before you open it.

School-night wind-down

The time apps go to sleep on Sunday to Thursday nights. Amara: 21:30. Noah: 20:30. Set it to the time you actually want the phone down, not ten minutes earlier as a buffer; the twelve-minute banner is the buffer.

School-day wake

The time apps open again on Monday to Friday mornings. Amara: 07:00. Noah: 07:00. Some parents set this to the time the child leaves for school, so the morning is for breakfast rather than YouTube; that is a reasonable use and the child sees it on their schedule.

Weekend wind-down

Friday and Saturday nights. Amara: 22:30. Noah: 21:15. An hour later than the school-night figure is the common choice; more than two hours later tends to make Sunday night hard.

Weekend wake

Saturday and Sunday mornings. Amara: 08:00. Noah: 07:00, because he is up anyway. This is the field most parents set and then forget, and it is worth revisiting when a child starts sleeping later.

Homework block

Off by default. When on, a start and end time and the days it applies to. Okafor: 16:30 to 17:30, Monday to Thursday. It pauses the same apps as bedtime and has its own always-allowed list, where Chrome and the school app live.

Always allowed overnight

Apps that stay open during wind-down, on top of calls, the alarm, the clock and the dialler, which are always open and cannot be removed. Amara: a music app. Noah: nothing extra. Shorter is better; every addition is a reason to pick the phone up at 22:00.

Always allowed during homework

A separate list for the afternoon block. Amara: Chrome, the calculator and the school’s assignment app. The point of two lists is that Chrome is open at 16:45 for an essay and asleep at 23:00 when it would be for something else.

Tonight only

A one-off later time for tonight, set from the parent app. Clears itself at the morning wake. This is the sleepover field, the birthday field and the “you can finish the film” field. The child cannot set it from their phone.

Set by

The name of the parent who last changed the schedule, shown on the child’s screens and in the panel’s command log. If a co-parent moves bedtime to 22:00 on a Tuesday, the log says who and when, and the child’s screen says “set by” the right person.

Where it runs

On the child’s phone, using the phone’s own clock, with the last confirmed version shown in the parent app. No signal, no Wi-Fi and no account connection are needed for tonight’s wind-down to happen; only a change to the schedule needs the phone to check in.

Bedtime questions

Questions parents ask about the phone bedtime.

Is a bedtime set automatically when I pair my child’s phone?

No. A newly paired phone has no schedule, no homework block and nothing that sleeps. The bedtime fields read “Not set” until you choose times, and the child’s transparency screen says so. Adding a child by date of birth suggests starting times for their age, but suggestions are not applied until you save them, and you can change every one before you do.

Can my child turn the bedtime off or change the clock to get round it?

The schedule cannot be edited from the child app. Changing the phone’s clock is the trick every child discovers, and because the schedule follows the phone’s clock it would move the bedtime with it; leaving Android’s automatic date and time switched on, which the setup checklist asks for, closes that door. Uninstalling the app does stop the bedtime, because the app does not hide from uninstallation or reinstall itself; you get a tamper alert instead, which is the conversation to have.

Does the phone bedtime drain the battery overnight?

No more than the app already does during the day, which is small. The schedule is a stored set of times checked against the phone’s clock, not a process that polls a server all night. The phone is not kept awake to enforce it. If a phone is losing noticeably more battery overnight, the device health page will show whether battery optimisation has been switched back on, which is the usual cause.

What happens if my child is mid-call when the wind-down starts?

Nothing. Calls are never interrupted, started or ended by the schedule. A call in progress at 21:30 continues until someone hangs up, and a call that comes in at 23:00 rings through. The dialler, the alarm and the clock are always open and cannot be removed from the always-allowed list. Only apps outside that list go to sleep, and even those simply pause rather than closing.

Can I set a different bedtime for each child?

Yes. Every schedule is per child: Amara’s 21:30 and Noah’s 20:30 are separate schedules with separate homework blocks and separate always-allowed lists. The week view shows one child at a time and you switch with the chips at the top. There is no family-wide bedtime that applies to every phone at once, because no two children in the same house have needed the same one.

Does the homework block know whether homework was actually done?

No. It removes the apps that compete with homework for an hour and leaves the ones you listed as useful; that is all. It does not see the screen, read documents or check that anything was submitted. If you want a reward for a finished reading session or a completed assignment, that is a tasks and rewards question, where the child marks it done and you approve with one tap.

Where the bedtime fits with everything else

The schedule decides which hours the phone’s apps are available; the features that decide how many minutes, which apps, and what was used sit beside it: tasks and rewards and app activity.

The bedtime schedule switches on once your child's phone is paired with your account, which takes about ten minutes with both devices on the table. The download and setup guide walks through every screen.

Set the time once, and let the phone keep it.

Choose a school-night time and a weekend time with your child in the room, and from tonight the phone goes to sleep on its own, with calls and the alarm still awake.

Android · Free account · Visible on your child's phone