Tap play in Wobble and a voice starts reading. It sounds like one thing, but it's the end of a long road. We tried every shortcut going, generic device voices, third-party reading APIs, the lot, and none of them held a child's attention through a chapter. So we made our own cast. This is what we learned, and how the Wobble voices ended up sounding the way they do.
why the obvious options didn't work
Every modern phone, tablet and laptop ships with a built-in reading voice. They're fine for a calendar reminder. They're not fine for a story. They're flat, they pace every sentence the same way, and they pronounce a child's name the same as a place name. Read a picture book in one of them and the room goes quiet for the wrong reason.
The off-the-shelf cloud voices are better, but they were built for adverts, sat-nav and corporate explainers. They sound like someone reading a script in a sound booth, not someone reading a bedtime story. And the more characterful ones tend to be locked behind enterprise contracts that don't make sense for a tool used in classrooms and on kitchen tables.
what we built instead
We made the Wobble cast ourselves. Emma, James, Sophie, Lily, George, Arthur and the rest are voices we designed from the ground up for reading children's books out loud. Each one has a brief, the warm narrator, the small bright sister, the deep slow giant, the wise old grandfather, and each one was tuned over hundreds of pages of real children's fiction until it stopped tripping over the bits that matter, names, dialogue, exclamations, the quiet pause before a punchline.
Because we own the cast, we can keep it consistent. The wolf is always the wolf. The narrator never suddenly changes pitch in chapter three. A child who hears Lily on a Tuesday in school hears the same Lily on a Saturday at home, on a different device, on a different network. The story sounds like the story, not like whichever bit of hardware happens to be in the room.
what this means in practice
When Wobble splits a page into narrator and characters, it draws from our own cast first. We picked a small, deliberate set rather than a giant catalogue, because variety wasn't the problem, distinctness was. Seven or eight strong voices that a child can tell apart beats fifty interchangeable ones every time.
We also kept the device's own voices available as a fallback, so the app still reads even if the network drops or a school device blocks ours. But the default, the one a child will almost always hear, is the one we made.
what you can do with this
- Open Wobble's voice picker and play the same line through two or three of the Wobble cast. Notice how each one changes the feel of the sentence, that's the point.
- Pick a narrator you actually like listening to. The narrator does most of the talking; if it grates on you it'll grate on the child too.
- Let the child choose the character voices. Ownership of the cast is half the engagement.
- If you're reading a book with strong character voices, lean into it, switch on character mode and let the cast do the work.
We didn't set out to build a voice studio. We set out to make a child stay with a book to the end of the chapter, and the voices were the thing standing in the way.