YouTube was not the thing I wanted to remove.
The friction was what happened after the first useful video.
A child can find something genuinely good about space, drawing, animals, science or music.
Then autoplay, recommendations and open search decide where the session goes next.
That tension became WonderKidTV.
The first decision was not to solve screen time
I did not want to build another product around the idea that all screen time is bad.
There is too much useful material on YouTube for that framing to make sense to me.
The narrower product question was:
How can I keep the useful content without handing the whole experience to the feed?
That question was more useful because it pointed toward something buildable.
A smaller choice set was the core product decision
WonderKidTV starts with channels and videos selected by parents.
Instead of giving a child the entire YouTube search and recommendation system, the app gives them a smaller set of choices that already fit the family’s expectations.
This is a real trade-off.
A smaller library reduces freedom. It also reduces drift.
I did not want to hide that tension behind a “safe for kids” label. The product is making a choice about where exploration should happen and where constraints are useful.
One family setting was too blunt
Different children need different limits, interests and levels of independence.
That led to per-child controls for watch time, approved channels, hidden videos, age settings, learning modes and search restrictions.
The important design idea was not “more controls”.
It was making the controls specific enough that one household did not need a single rule for everyone.
Watching needed a small interruption
Another problem appeared while building.
A useful video and an autoplay video look identical in a watch-history counter.
So WonderKidTV includes learning goals and questions linked to viewing.
The aim is not to turn every video into a test.
It is to create a small pause between watching and moving on.
A useful video should leave something to explain, question or remember.
Visibility helped more than another blanket rule
Screen-time conversations are difficult when the only number is total minutes.
So the app added watch reports that show topics, channels, videos watched, videos skipped and viewing history.
Those reports do not tell a parent whether every minute was valuable.
They provide better raw material for the conversation.
The hard part is choosing how much control to remove
Building a parent-guided product creates its own failure modes.
Too much control can remove curiosity.
Too little control can recreate the same open feed the product was meant to change.
Too much reporting can become surveillance instead of useful visibility.
That is the part I find most interesting now.
The product problem is no longer “How do I block YouTube?”
It is:
Where should the product guide, where should it constrain and where should it get out of the way?
ThinkBySketch 
Leave a comment