Most screen-time advice is about minutes. Minutes are easy to count, which is why they get counted, and they are close to useless on their own. Twenty minutes of a child tapping, saying words out loud and being asked questions is a different activity from twenty minutes of autoplay, and calling both “screen time” flattens the only distinction that matters.
Two better questions:
- Does the screen ask my child to do anything?
- Who decides what comes next — me, my child, or the app?
Question one: does it ask anything?
Passive is not evil. A child watching a film is fine. But the default state of a phone handed to a four-year-old is a stream that never asks anything, and a child can be in front of it for forty minutes without saying a word or making a single decision.
Interactive means the screen stops and waits. Tap the one that starts with M. Sort these into land and sea. Say the word out loud. Clap on the fourth beat. Trace the letter with your finger. The child is producing something, not just receiving it, and you can hear the difference from the next room — an interactive session is noisy.
There is a shallow version of this worth spotting. Tapping anywhere to make confetti is not interaction; it is a slot machine. The test is whether the tap could have been wrong. If every tap produces a reward, the child is not thinking, and you will see it in how quickly they get bored.
What a good wrong answer looks like
If the screen asks questions, then how it handles a wrong answer is most of its character.
The bad version is a red cross and a buzz. The child learns one thing — that they failed — and nothing about the answer. Worse, at four, they often learn to stop guessing, which is the opposite of what you want.
The good version has three parts, in order:
- Something true and kind about the thing they chose. They put the fish on land: “Fishes love to swim — they always live in water!” Not a correction. A fact about their choice.
- A walkthrough. The screen shows them how to get there, and where it can, the child taps along with it rather than watching.
- The right answer, tapped by them. It glows, they tap it, it celebrates. They finish the moment doing the correct thing with their own hand.
That takes four times as long as a buzzer and it is worth every second. It is also the reason we have no red anywhere a child can see: a wrong answer wobbles gently, the right one glows green.
Question two: who decides what comes next?
This is the one I care about more, and it is the reason the app exists.
A feed decides. The moment a video ends, something else begins, chosen to keep your child there. No child has ever won an argument with a feed, and neither have most adults. The minutes were never the problem — the missing ending was.
The alternative is boring and it works: a fixed, finite list, chosen by you, that runs out.
In practice that means the parent puts a handful of things into a plan — three items, five items, whatever the evening can take — and the child’s side of the app plays exactly that and then stops. No suggestions. No “up next”. No thumbnails of things they did not ask for. When the list is finished, the character waves goodbye on a calm screen with nothing else on it: no replay button, no next, no grid. That screen is the single most important one in our app, precisely because it is the emptiest.
The handover is deliberate too. Getting into the child’s side is a slide gesture on the parent’s home screen; getting back out needs a press-and-hold or a passcode. Not because a four-year-old is a security threat, but because “how do I get back?” should never be a thing a child solves by tapping around.
A short checklist for any kids app
- Does it ask the child to do something, and can that thing be wrong?
- When it is wrong, does it teach, or does it buzz?
- Does it end, or does it always have one more thing ready?
- Can the child reach a shop, a link, a video suggestion, or an advert from inside it?
- Is there a timer or a life count pressuring them? (There should not be.)
- Can you see what they actually did, in plain words?
- Does the microphone, if there is one, say what it does with what it hears?
You can run that list against any app in about two minutes, and it is a better use of your attention than counting minutes.
The part that is on us, not the app
None of the above tells you how long. That is still your call, and it depends on the day, the weather and whether anybody slept.
What a bounded session buys you is that the end is not a fight. The list ran out. That is a different conversation from taking a device away mid-video, and it is the reason the “ten more minutes” negotiation mostly disappears.
If you want the other half of this — what a child is actually learning during those interactive minutes, and how to tell without a percentage — what honest learning progress looks like covers it.
Make this in Dinomy
Everything a child sees, a grown-up put there. You create songs, stories and lessons, review them, and queue them into a named plan — Bedtime, Car Ride, whatever you keep reusing. Then you slide to hand the phone over. Your child’s side is a locked room: big wordless buttons, no reading required, no suggestions, no autoplay chain, no shop, no adverts, no links out. It plays your list, it celebrates, and it stops. Getting back to the parent side needs a press-and-hold or your passcode.
