From consumer to creator: rethinking screen time

Why counting hours misses the point

“How much screen time?” is usually the first question a parent asks, and it is the easiest one to ask because it produces a number. Forty minutes before dinner. Two hours on a wet Sunday. Numbers are simple to track and simple to argue about at the table.

The trouble is that the same number can describe two very different afternoons. A child who spends ninety minutes watching short clips and a child who spends ninety minutes building a small game in Pocket Code have both logged “an hour and a half of screen time.” The phrase tells you nothing about what actually happened in it.

The research on screen time is genuinely mixed, and anyone who hands you a clean, safe number of hours is telling you more than the evidence supports. What comes up more often, across studies that disagree on plenty else, is that what the time is spent doing matters at least as much as how much of it there is. That is a harder thing to put on a chart than a countdown timer, but it is the thing you can actually watch happen.

What creating looks like in the room

You do not need to understand what is on the screen to notice the difference between consuming and creating. It shows in posture, pace, and what your child says out loud.

A child who is consuming tends to sit still, react to the screen rather than direct it, and keep going well past the point you would expect them to stop, because there is always something else queued up next. Ask what they are watching and you often get a shrug: the content was chosen for them, not by them.

A child who is creating looks different. There are pauses, staring at the screen doing apparently nothing, which is usually thinking rather than stalling. There is talking, to themselves or to you, narrating what they are trying to do (“I want the cat to jump when I tap it”). There is a kind of frustration that watching rarely produces, because a game that will not do what you wanted is a problem, and a boring video is not, you just swipe past it. And there is a particular kind of pride when something finally works: wanting to show someone, rather than just wanting the next thing to appear.

None of this requires you to look at the screen at all. Most of it you can hear from another room.

How to be part of it without turning it into homework

The instinct once you notice a child building something is to get involved, and it is worth resisting a little. A parent leaning over and asking “have you tried…” every few minutes turns a project into a supervised task, and most children lose interest in supervised tasks faster than they lose interest in their own.

Showing interest without steering tends to work better. Ask what the game is about before asking how it works. Ask to play it once there is something to play, even if it lasts three seconds and is mostly broken. Sit nearby doing something else, so that “look what happened” has somewhere to go. Pocket Code is built so a child can look things up and try again without an adult who can code standing over their shoulder, and ourPocket Code starter path is written for the child, not for you, for that reason.

Where a parent can help without any coding knowledge at all is time and space: not interrupting a project that is going well because dinner is nearly ready, not booking something else across the one free hour of the week, and not asking every single day whether the game is finished yet. Long projects need long, unbothered, occasionally boring stretches of time, and that is something you can protect without touching the screen.

When it stalls or gets abandoned

Most projects a child starts do not get finished. That is ordinary, and worth saying plainly, because it is easy to read an abandoned project as proof the whole exercise failed. A half-built game left for a new idea two days later is not evidence that your child is not “the creative type,” any more than a half-read book or a half-built model would be. Interest moved somewhere else.

What is worth noticing, when it is visible, is the reason behind the drop-off. Giving up because the idea turned out to be more work than expected is a normal part of making things, and pushing a child to finish something they have lost interest in tends to teach the wrong lesson, that creating is a chore with a deadline attached. Giving up because they hit a wall with no way past it, and nobody nearby to ask, is a different situation, and probably means the next attempt needs a bit more scaffolding: a simpler starting project, or sitting through the frustrating part together once rather than leaving them to it every time.

Either way, a stalled project is rarely the end of the story. Children who make things tend to start several before one goes anywhere, and the abandoned ones are not wasted time. They are usually where the next attempt gets easier.

What we don't know

It is worth being plain about the limits here. The idea that what a child does matters more than how long they do it is a reasonable, widely discussed position, not a settled finding with a number attached. We have not run a study on this ourselves, and we are not going to invent one to sound more certain than the evidence allows. What we can offer is a way of looking at the time your child already spends on a screen that goes beyond the stopwatch, plus one specific, free way to try the creating side rather than the consuming one: Pocket Code, which a child can pick up on a phone you already own. For a broader starting point, theAt-Home hub covers the rest of what parents ask us about.