Last Tuesday, Sarah in Portland told me she'd been lying to her pediatrician. "I say thirty minutes a day," she said. "It's more like two hours. But half of that is her speech app and Bluey, and the other half is YouTube rabbit holes about trucks." Her daughter, Maya, is four, autistic, and has about forty spoken words. Sarah wanted a number. How many minutes is okay? What I told her is what I'll tell you: the minutes don't matter nearly as much as what's happening during them.
Speech apps count as screen time. Obviously. But lumping a ten-minute interactive speech session in with ninety minutes of YouTube autoplay is like saying a salad and a milkshake are the same because they're both food. The category matters. The context matters. What the screen replaces matters most of all.
I'm a dad who uses screens with my autistic daughter. I think about this carefully because the stakes are real, and because I've read enough conflicting advice to fill a small library. Here's the honest framework.
The research is more nuanced than the headlines
The American Academy of Pediatrics recommends limiting screen time for kids under two (except video chat with family) and one hour or less of high-quality programming for ages two to five. But the more recent emphasis has shifted toward content quality and co-engagement rather than raw minutes. That shift matters.
Co-watched and interactive content has different effects than passive solo watching. A toddler watching a show with a narrating parent is closer to a book-reading interaction than to passive consumption. Some studies show language gains in this scenario.
Background TV has measurable negative effects on language development, particularly for kids under three. A TV running during dinner is worse than the same kids watching a show together for twenty minutes with intention.
For autistic kids specifically, the research is sparser and more mixed. Some studies suggest higher screen time correlates with later language development. Others suggest screen-based interventions can be effective when designed well. The takeaway nobody wants to hear: quality, context, and what the screen is replacing all matter more than total minutes. There is no magic number.
Three buckets, not one
For practical purposes, I think about screen time in three categories.
Bucket 1: Active, co-engaged, brief. A parent and child looking at a short, language-rich show together. The parent narrates, comments, points. A speech app used for ten focused minutes with a parent nearby. This is the lowest-cost category. It can actually be net-positive.
Bucket 2: Active, solo, brief. A child using a speech app or educational game on their own for a defined session. Less ideal than co-engaged, but still active (they're doing something, not just watching).
Bucket 3: Passive, solo, long. YouTube autoplay. Endless reels. Background TV. This is where the costs pile up.
A ten-minute speech app session falls in bucket 1 or 2, depending on whether you're sitting next to your kid. That is a fundamentally different animal than ninety minutes of algorithm-curated video.
Forget "how much" and ask "instead of what"
This is the question that actually matters. Not "how much screen time?" but "what is the screen replacing?"
If the screen replaces floor play with a parent, sensory play, reading together, sleep, or meals with conversation, it's net-negative regardless of content quality. Full stop.
If the screen replaces sitting bored, a parent who is genuinely unavailable (cooking dinner, taking a work call), or another lower-quality activity, the screen can be net-positive. If the content is good.
That's the math. Ten minutes of a well-designed speech app while you cook dinner, instead of YouTube autoplay, is a clear upgrade. Ten minutes of the same app instead of sitting on the floor reading together is a wash or a downgrade.
Audit what the screen displaces. Not just the clock.
What "high-quality" actually looks like
The phrase "high-quality content" gets thrown around like confetti. Here's what it means concretely for speech apps:
Designed by people who understand child development. The app shows evidence of SLP input, developmental knowledge, ND-affirming design. Not just slick graphics.
Interactive, not passive. The child does something. Speaks, taps, decides. Passive watching doesn't count as active screen time even if the narrator sounds educational.
Co-engagement friendly. Sessions are short enough and structured enough that a parent can sit nearby and engage. No autoplay. No infinite scroll.
No ads or in-app purchases targeted at the child. COPPA compliance, transparent monetization.
Predictable pacing. Slow enough for ND processing time. Not the rapid-fire, dopamine-spiking rhythm of attention-grabbing kid apps.
LittleWords meets these criteria by design. Most TV does not. Most YouTube does not. Most "educational" kid apps land somewhere in the murky middle.
Co-engagement is the multiplier (and it's free)
The single biggest thing you can do to make screen time productive costs nothing. Sit next to your kid.
Co-engagement doubles the language input (the content plus your narration). It lets you pause and label moments. It connects what's on screen to real life. It models screens as a shared activity. And your physical presence provides co-regulation, which matters enormously for ND kids.
Here's the thing: a child who watches Bluey alone is consuming content. A child who watches Bluey with a parent who narrates, pauses, and says "look, Bingo is frustrated just like you were at the playground" is doing language work.
The same applies to speech apps. LittleWords used with a parent sitting nearby is more effective than LittleWords used solo. Not because the app needs you, but because you help bridge app moments to the rest of the day.
Background TV: the one to actually cut
If you only change one screen habit, make it this: turn off background TV. The TV on while the family eats. The show playing while the kids build blocks in the same room. This is the screen time category with the clearest negative effects in the research.
The mechanism is straightforward. Background TV reduces parent talk. Adults talk less when a TV is on. Kids hear less language. Less language input means slower language development.
Turn it off when nobody's watching it. Honestly, this matters more for language development than choosing between Bluey and Daniel Tiger.
Rules that have actually worked in our house
These are family-specific. Yours will look different. The principle underneath them is simple: screens have a purpose, and when the purpose is done, the screen is done.
No screens during meals. Meals are language-rich opportunities. Protect them.
No screens in the hour before bed. The sleep effects are real. Screens close to bedtime reduce sleep quality, and sleep deprivation undermines everything else.
Co-engaged when possible. If we put on a show, we watch with her, at least for the first few minutes.
One activity at a time. No background TV during play. No app while watching a show. The brain does one thing well or two things poorly.
Specific, finite sessions. Ten minutes of LittleWords. One episode of Bluey. Not "let's see what's on YouTube."
Screens for transitions. When we need to do something and she needs to be occupied, the screen has a job. We use it intentionally and turn it off when the job is done.
A note on screens as regulation (not deficit)
Some ND kids use screens as a regulation strategy. Watching a familiar show, looping a favorite scene, replaying the same game. These behaviors can be genuinely regulating. Not stimming-as-deficit but stimming-as-self-care.
Suppressing screen-based regulation entirely can leave a child without tools they need. The better approach:
- Allow screen-based regulation when it's genuinely needed
- Pair it with co-engagement when possible
- Watch whether the screen helps the child return to other activities afterward, or whether it's replacing them entirely
A child who watches Bluey for thirty minutes when overstimulated and then rejoins family activities is using the screen well. A child who watches for three hours and refuses to do anything else may be using the screen as avoidance. That's a different conversation, and probably one worth having with a professional.
Why LittleWords is built the way it is
LittleWords is designed for short, intentional sessions. The recommended session length is ten minutes. The pacing is deliberately slow to allow for ND processing time. There is no autoplay, no endless content loop, no engagement-maximization tricks baked in.
We don't want to be a screen-time-maximizing app. We want to be a ten-minutes-a-day-of-language-work app. Different goal. Different design choices at every level.
When to get professional input
If your child is on screens for many hours a day and you're concerned about language development, an SLP evaluation can help identify whether language is being affected and what the right intervention looks like. The screen-time conversation often comes up naturally in those evaluations, and a good SLP won't shame you. They'll help you problem-solve.
FAQs
Is ten minutes of a speech app a day too much? No. Ten minutes is well within any reasonable screen time guidance for kids over two, especially with co-engagement.
Does Bluey count as language work? Co-watched with a parent who narrates and engages, yes. Watched alone, it's closer to passive content. Not harmful, but not language work either.
My child is under two and uses an iPad daily. Am I making a mistake? The AAP guidance is to limit screens under two. If the iPad is the only thing your child engages with, that's worth reflecting on. If it's part of a varied day with parent interaction, sensory play, and reading, it's less concerning.
Can a screen activity ever build language? Yes, with co-engagement and the right content. Solo passive screen time does not build language. Interactive, co-engaged screen time can.
How do I know if my child's screen use is a problem? Watch for: refusal to engage off-screen, escalating screen time, screens as the only regulation strategy, language regression. Any of these is a signal to dial back and possibly get professional input.
Is YouTube ever okay? In small, intentional doses with content you've chosen (not autoplay), it can be fine. The problem is the algorithm, not the platform. Curate a playlist, set a timer, sit nearby if you can.
---
Related reading: Best speech therapy apps hub · Speech therapy at home for autistic kids (pillar guide) · Bluey and speech therapy · Are speech therapy apps worth it
Related Little Words guides
- Parent GuidesBrowse all 474 articles
- 10-Minute Speech Practice for Toddlers Who Won't Sit StillRelated parent guide
- What 10 Minutes a Day Actually Did for Her SpeechRelated parent guide
- 3-Year-Old Speech: Strangers Should Understand 75%Related parent guide
- 4-Year-Old Still Hard to Understand: Normal or Not?Related parent guide
- How to Get an AAC Device Through InsuranceRelated parent guide
- AAC for Autism: A Parent's Plain-English Starter Guide (PECSRelated parent guide
- AAC for Autism: A Plain-English Starter GuideRelated parent guide
- AAC for Toddlers: When and How to StartRelated parent guide