Why we narrate every word, and what moves while it plays

Most children's story apps are built like cartoons. Something moves on every screen, a character reacts to every touch, and there's usually a reward noise. It's very good at holding attention.

Story Beaver moves too. The difference is what the movement is for.

The word being spoken lights up

The narration is recorded as real speech and timed to the page. As it plays, the word being spoken lights up, for exactly as long as it's being said.

That's the part that matters for a child learning to read. They hear a word and see it at the same moment, in the same place on the page, over and over, until the connection between the sound and the print is one they own. Nothing has to be configured first. A four year old should be able to open a book and be reading within a few seconds.

Tap any word and hear it

The text is the thing you can touch. Tap any word and it says that word. For the handful of words a book is teaching, it also explains what the word means, in speech, in a sentence a child can follow.

This is the interaction we spent the most time on, because it's the one that turns a listener into a reader. A child who is curious about a word can get an answer immediately, without waiting for an adult to finish what they're doing, and without an adult having to already know the answer.

That immediacy is the point.

The art moves on the story's clock

The art in Story Beaver does move, and it's worth being exact about that, because "story apps shouldn't animate" is the wrong lesson and we don't want to be selling it.

Characters and objects arrive, sway, drift and settle as the story is read. Their timing is cued to the narration: a thing tends to move when the sentence about it is being spoken. So the cup that arrives on the page arrives when the text says it arrives. It doesn't bob because a timer went off, and it doesn't bounce to pull a wandering child back to the screen.

That distinction is the whole design. A cartoon is built so the animation is the product and the words are decoration. Here the narration is the spine, and the motion hangs off it.

If a child wants the pages completely still, they can have that. There's a motion setting in the app, and the device's own reduced-motion preference is respected either way. Both turn the movement off, and the reading works exactly the same without it.

What we left out

No advertising. No streaks, no daily goals, no badges for reading. No chat, no profiles, no leaderboards. Nothing that turns reading into a performance for an algorithm.

There's a hint that appears if a child sits on a page for a few seconds without doing anything, and that's the limit of it. Nobody is trying to win their attention back.

The audience is four years old. The defaults have to be the safe ones, and the app should be boring in the ways that matter.

The books work on a plane

A downloaded Story Beaver book contains everything it needs: the art, the text, the narration, the word help. Once a book is on the device it reads with no connection at all.

That's partly practical, because cars and planes are where a lot of reading happens. It's also a design statement. A book that stops working when the signal drops teaches a child that books are fragile. These aren't.

Before a book is offered for offline reading, the app checks it against a published hash and confirms it's complete. That check exists so a download that went wrong can never present itself as a working book.

You can read the full privacy notice for exactly what the app does and doesn't collect, or see how the books are made.

← All posts