Choosing a kids app for a child who cannot read

Handing a phone to a three-year-old is a different problem from handing it to a nine-year-old, and most advice about children's software is written for the second. A child who cannot read yet navigates by picture, by sound and by memory of where things were, and an app built for readers fails them in ways that are not obvious to an adult testing it.

A kids app is any application built for a child rather than adapted for one, and choosing a kids app for a pre-reader comes down to four questions, and only one of them is about content. The others are about how the app behaves when a child does something unexpected, which is most of the time.

The four questions

Can it be operated without reading? Icons that mean something, audio labels on buttons, and a structure shallow enough to be remembered rather than navigated.

What happens on a wrong tap? A pre-reader taps everything. An app where a stray tap opens a store, a settings screen or a link is not designed for this audience regardless of how the main content looks.

Does it end? A story that finishes is different from a feed that does not. Software with a natural stopping point does not require an adult to be the one who ends it, which changes the whole dynamic.

Who is it actually for? Some children's apps are built to be shown to parents in a store listing and are unpleasant to use. Others are built for the child and are plain in screenshots.

A pre-reader cannot read the way out. Every screen needs an obvious exit, and every stray tap needs to be harmless.

What to check before installing

Six checks before installing a kids app, and the first three take a minute on the store listing.

• The price model. Free with in-app purchases is the pattern most likely to produce an accidental spend and the most likely to interrupt with prompts. Paid once, or free with no purchases, behaves better.
• Advertising. Ads in software for young children are a hard problem — a child cannot distinguish an advert from content, which is exactly why the practice is regulated in many places.
• What it collects. Read the privacy label. Software for children should collect almost nothing, and anything used for tracking is disqualifying.
• Whether it needs an account. For a young child there is rarely a reason.
• Whether it works offline. Cars, planes, waiting rooms — the places this is used most.
• Whether an adult gate exists, protecting settings and purchases with something a small child cannot pass.

Audio-first is the format that fits

For pre-readers specifically, the strongest kids app category is the one that does not require the screen at all.

A story read aloud works whether the child is looking or not, travels to a car or a bedtime, and can be repeated indefinitely without the parent reading it again. It also does something screen-based apps cannot: it leaves the child's hands and eyes free.

Three things separate a good audio story app from a mediocre one:

Complete narration, not text with a play button. The whole piece read properly, so a child who cannot read is not dependent on an adult.

Short pieces with clear boundaries. One story, one sitting. An app like Tales Home is structured this way — each story with a full narration — which matches how the format is actually used rather than how a catalogue looks.

Repeatable without friction. Children want the same story forty times. Getting back to it should be one tap from opening the app.

The second point matters more than people expect. A fifty-minute audio file is unusable at this age, because losing your place means losing everything, and a child cannot scrub back to where they were.

What "educational" does and does not mean

The word is unregulated and appears on nearly everything, so it carries no information on its own.

What genuinely helps at this age is narrower than the marketing suggests: language exposure through hearing lots of words in context, cause and effect through simple manipulation, and shared attention — an adult and a child looking at the same thing and talking about it. That last one is not a property of software at all.

What to be sceptical of: claims about accelerating reading, apps that quiz rather than play, and anything measuring a young child's progress. A pre-reader tapping the correct picture has learned which picture to tap.

The honest framing is that good software at this age is pleasant, harmless and finite. Claims beyond that are marketing, and the absence of such claims is not a defect.

Setting it up so it stays safe

Four settings, once, before handing the device over with any kids app on it.

1. Turn on the platform's guided or kids mode, which locks the device to one app until an adult exits.
2. Disable in-app purchases at the system level, not just in the app. This is the setting that prevents the story everyone has heard about.
3. Set a screen time limit if that suits you, and know that the app ending on its own works better than a timer interrupting.
4. Check the app's own settings for anything that opens outside it — links, social features, a store — and turn them off.

The second point is worth doing regardless of which apps you install, because it applies to every app on the device, including ones added later.

How to try one before committing

Ten minutes with the app yourself, before the child sees it, catches almost everything.

Tap everywhere. Corners, edges, the same button repeatedly, two places at once. You are looking for anything that leaves the app — a store, a browser, a settings screen with no obvious way back.

Try it with the sound off, then with the sound loud. Some apps are unusable silently and unbearable at volume, and both matter in a house.

Wait without touching it. Some apps prompt, animate or make noise when idle in order to pull attention back. That behaviour is designed against the child, and it is invisible in screenshots.

Look for the exit from three levels deep. Go as far in as you can and see how a child would get out. If the answer is a small back arrow in a corner, they will not find it.

Check what a parent sees. Some apps put a review prompt, an upsell or a newsletter box where a child will reach it.

Then hand it over and watch once without helping. What a child does in the first two minutes tells you more than any review, and the thing you notice is usually not the thing you were checking for — a button they cannot reach, a sound that upsets them, a screen they get stuck on and quietly give up at.

When to hand it over at all

Not a software question, and the most consequential decision here.

The research is genuinely mixed and the strongest finding is unglamorous: what the child is doing matters more than the total time, and doing it with an adult present matters more than either. A story listened to together is a different activity from the same story alone, even though a screen-time counter records both identically.

Practically, that argues for co-use where it is possible, for content that ends by itself, and for treating the device as an occasional activity rather than a default one — none of which requires policing minutes.

More app picks in best tools, comparisons in comparisons, and reviews in reviews. The WHO guidance on young children and screens is a reasonable starting point for the underlying question.

The short version

For a child who cannot read, judge a kids app on whether it can be operated without reading, what a stray tap does, whether it ends, and who it was really built for.

Prefer no advertising, no account, offline function and an adult gate on settings and purchases — and disable purchases at the system level rather than trusting any individual app. Audio stories fit this age better than anything on a screen, provided they are short, fully narrated and one tap from playing again.