Building a kids' app while trying to limit our own kids' screen time. How do you square that?

We build a learning app for small children, and we also believe young kids need less screen time, not more. That tension shapes a lot of our decisions: daily time limits and a bedtime lock that parents set per child, rounds that end instead of looping forever, no notifications, and drawing lessons that tell kids to pick up real paper.

We still don't know where the line is. Is a "good" kids' app one that kids use a lot, or one they put down easily?

If you have kids, or build products for them: what rules or design choices have actually worked for you, and which ones sounded good but didn't survive real life?

43 views

Add a comment

Replies

Best

Not a kids' app, but we hit a version of this with Victra Careers. A job search tool "wins" when someone finds a job and stops opening it, so time spent is a bad goal for us too. Your "rounds that end instead of looping" sounds like the right instinct: a clear point where the task is done. Curious, do parents notice the bedtime lock more than the daily limit?

 honestly no numbers, we don't collect usage analytics on that. my guess is bedtime, it hits at the same time every night so it turns into routine, the daily limit kinda floats around. one thing that helped with both: 2 min before either kicks in the screen slowly goes warm yellow, no popup, so it doesn't feel like a door slamming shut

For me, a good app promotes anti-app behaviour, but then you can't let kids stay aloof from the digital environment. You gotta move with time. Research suggests that 20 minutes of screen time is overwhelming for a kid, and I planned a "no screen" routine for mine. But that changed soon. Since yours is a learning app, I look forward to seeing how you build it. Maybe healthy challenges for kids to stay away from screens for the next XX hours could be a feature. Children take games seriously.

 the no screen plan bending pretty fast sounds very real tbh. an off-screen challenge is a nice idea, nothing like that decided on our side yet. closest thing we have now is the drawing lessons ending with "now try it on real paper", and kids do take that part seriously

We build a family app too, and the choice that held up best for us was putting the stop point inside the activity instead of on a clock. "Two rounds, then done" is something a small child can see coming. A timer that cuts in mid-round feels like losing something, even with a warning.

The one that sounded good on paper: letting kids earn extra screen minutes on their own. Without a parent in the loop it turns into a points economy to game. We kept earned time, but every request needs a quick yes from a parent, and the app itself doesn't block anything.

On your question, I'd judge a kids' app by what happens after it's closed. If the drawing really moves to paper, that says more than minutes in the app. Does the warm-yellow fade work as well for 3-year-olds as for the older kids?

 no real data on that, so just a guess: older kids read the yellow on their own, 3 year olds probably only after a grown-up has said "yellow means last one" a few times. agree on putting the stop inside the activity, a clock is pretty invisible at that age

the warm yellow fade is a gentle way to say it's ending without a popup. can a child see how many rounds are left before a session starts, or only as it winds down?

One thing I'd look at is the very last screen a child sees. The warm fade and rounds that end handle the lead-up, but what happens at the stop matters just as much: if the app goes blank or snaps shut, it reads as being cut off, whereas a clear "all done" moment (a character going to sleep, a sticker, "see you tomorrow") makes the ending feel like a finish rather than a loss. That's a design bet I'd test rather than a rule, since I haven't tried it with kids myself. It might also be worth showing parents a simple preview of that stop screen when they set the limits, so they know what their child will see.