Most screen-time limits fail in one of two ways. Either the child finds a way around them in an afternoon, or the rule holds and the household pays for it in daily arguments. Both outcomes are usually decided before the limit is set, by which kind of limit it is and how it was agreed.
Here is what distinguishes the rules that survive.
The three kinds of limit, and what each is for
Daily caps
“Two hours a day.” Simple to state, simple to understand, and the weakest of the three in practice.
The problem is that a daily cap treats every minute as interchangeable. Forty minutes of video before school and forty minutes after dinner are very different things, and a cap cannot tell them apart. Children also learn quickly that a cap is a budget to be spent strategically, which turns every session into negotiation about whether this one counts.
Daily caps work best as a conversation prompt rather than an enforcement mechanism: a number everyone can see, checked weekly, so that “you are on screens a lot lately” becomes a fact rather than an opinion.
Bedtime windows
“No phone after 9:30pm.” This is the limit with the best track record, for three reasons: it is unambiguous, it does not require anyone to count anything, and it protects sleep, which is the thing most worth protecting.
It is also the easiest to enforce without technology at all — the phone charges in the kitchen. Every serious parental-control product implements a bedtime schedule, Family Link included, and it is usually the first feature worth turning on.
Per-app limits
“Thirty minutes of TikTok, unlimited for the reading app.” The most precise and the most work. Per-app limits need constant maintenance as apps come and go, and they push children toward whichever app is not on the list rather than toward less screen time.
Where they genuinely help is with one specific app that has become a problem. As a general system they tend to collapse under their own admin.
How the measurement actually works
This part determines what is possible on each platform, and it is worth knowing before you buy anything.
Android exposes app usage statistics through the operating system. With the user’s permission, an app can read how long each other app spent in the foreground. This is how screen-time features on Android are built, Kidslen’s included. Two consequences: the numbers are the operating system’s own, so they cannot be edited away by clearing a history inside an app; and the permission is visible in settings, so the child can see that it was granted.
iOS does not expose anything comparable to ordinary apps. Apple’s Screen Time is built on a framework called Family Controls, and third-party access requires a specific entitlement from Apple. This is why so many products are richer on Android, and why Kidslen measures app screen time on Android today and not yet on iPhone.
The practical version: on Android, measurement is solid and blocking is complicated. On iOS, Apple’s own Screen Time is strong and everyone else is working through Apple’s framework.
Blocking in 2026: the honest state of it
Many Android parental-control apps have historically implemented blocking through the Accessibility API — the system service built for screen readers and switch access, which can see what is on screen and act on it. It was the only practical route to “close this app when the limit is reached.”
That route is narrowing. Android 17’s Advanced Protection Mode restricts non-accessibility apps from using the Accessibility API, and as The Hacker News reported, this directly affects parental-control apps that rely on it for screen-time enforcement and app blocking. It is a good security change — that API is also how a lot of Android malware works — and it makes a common blocking technique less dependable.
So if you are choosing a product in 2026 on the strength of its blocking, ask how the blocking is implemented and what happens to it under Advanced Protection.
Kidslen does not block apps. It measures, it sets limits, and it alerts when a limit is reached. That is a real gap compared with Qustodio or Family Link, and we would rather name it than describe an alert as enforcement. The FAQ says the same thing.
Three ways a reasonable limit still fails
It counts the wrong thing. A cap on “screen time” that includes a video call with a grandparent and a homework document is a cap nobody will respect, correctly. Decide what you are actually trying to reduce before you pick a number, and exclude the rest explicitly.
It has no visible clock. If the only person who knows how much time is left is the parent, the limit arrives as an interruption rather than as an expectation. Children who can see their own remaining time stop mid-video far more often than children who are told to stop.
It never changes. Screen-time rules age badly. A number that was right for a ten-year-old in winter is not right for the same child in the school holidays, and enforcing it unchanged teaches that the rule is about authority rather than about sleep, homework or attention.
Why an unnegotiated limit gets bypassed
Bypassing is not primarily a technical problem. A child who wants around a limit has options that have nothing to do with hacking: a friend’s phone, a school device, a browser instead of the app, a second account, the family tablet. You cannot close all of those, and the effort of trying is exactly what turns a household into an adversarial system.
The research on adolescent online safety is fairly consistent here. Covert or purely restrictive monitoring damages trust, raises family conflict, and often fails to deliver the protection it promises; the direction researchers recommend is transparency, teen participation and respect for growing autonomy (2504.15533, 2503.22995). UCL researchers have warned separately that unofficial parental control apps put children’s safety and privacy at risk.
Put plainly: a rule your child helped write is a rule with one person defending it instead of one person attacking it. That is worth more than any enforcement feature.
A limit that tends to hold
Four properties, in rough order of importance.
- Negotiated, not announced. Ask what they think is reasonable first. You will often get a stricter number than you expected, and you will always get better compliance.
- Anchored to events, not to a stopwatch. “Nothing after dinner until homework is done” and “phone charges in the kitchen overnight” beat “ninety minutes” because nobody has to count.
- Visible to both sides. If the child cannot see the same number you can, every disagreement becomes your word against theirs. This is why Kidslen shows the child the same dashboard the parent sees, with a permanent banner and a consent record they can revoke — the numbers are shared facts, not evidence one side holds over the other.
- Reviewed on a schedule. A limit set at eleven and never revisited is a limit a fourteen-year-old is entitled to be angry about. Put a monthly review in the calendar and let it move.
What to do this week
- Start with bedtime. One rule, one time, no counting.
- Look at the actual numbers for a week before setting a cap — most families guess wrong in both directions.
- Agree the rule out loud, and write it somewhere both of you can see.
- If you also want to know what is being watched rather than for how long, read can you actually see what your child watches on YouTube? — the answer has limits worth understanding before you rely on it.
- For younger children on YouTube Kids, see YouTube Kids: what parents can and cannot see.
- If you want the measurement side set up transparently, the setup guide walks through it, and the app is on the download page.