Why I built Namesake

My daughter wanted a story about a narwhal who was also, somehow, a firefighter. And unicorns. There are always unicorns. It was 7:45pm, lights were about to go off, and that was the brief.

Our bedtime needs a little explaining, because it's where this whole thing came from. We read together. Three books, or chapters now she's moved on to bigger ones. Sometimes a story I make up on the spot. Then the lights go off and she has about forty-five minutes of audio playing while she drifts off.

Every family's ritual is different. Ours has ended up this way mostly by accident. I love the reading part. It's the audio in the dark bit I've been fiddling with.

It started on the edge of her bed

I wasn't trying to build an app. I was sitting with my phone tilted away from her, typing into ChatGPT and reading back whatever came out, because the stories I invented myself had started coming out the same shape. Same beginning, same rescue, same tidy landing.

I wanted ideas. A twist I hadn't thought of. Somewhere for the thing to go next when I'd run dry three sentences in.

But I kept repeating the setup. Her age. Her toys and imaginary friends. Whatever she happened to be into that week. I could get a story out of it, but I was still doing all the work of carrying her little world from one evening to the next.

Meanwhile, her Toniebox was playing the same handful of stories it had played for months. She was bored of them. So the obvious thought arrived: why couldn't the new stories we'd been making together be the thing playing after lights-out?

The hard part was everything around the story

Getting a story narrated is possible on your own. I did it. Paste the text into ElevenLabs, generate the audio, download it, work out how to get it onto something that plays in her room. Build a playlist so it doesn't stop dead after four minutes. Set a sleep timer so it isn't still going at midnight.

Every step is doable. Stacked together at 7:45pm, they become a small administrative job at exactly the wrong moment.

That's where Namesake came from. You give it the ingredients, check the story, and it becomes a narrated book on your child's shelf, ready to play again.

The name has changed since I first wrote about it. The reason for building it hasn't.

A little world you don't have to explain again

Namesake remembers the child's profile and the companions you've added: people, pets, toys, imaginary friends. You can choose who's in tonight's story, pick a theme, or give it your child's own idea. Some nights that might be a detailed brief about a firefighter narwhal. Other nights you just want a story.

You can now use photos to make illustrated versions of your child and their companions. I like that a familiar teddy or the family dog can become recognisable on the cover as well as in the story. It gives all those details you've entered somewhere to live.

The library has become a bigger part of the app than I initially expected. A story doesn't disappear after one listen. It sits alongside the others, with its own cover, and you can put a few together for tonight.

My daughter can't read yet, so she chooses the stories she likes entirely by their covers. She remembers the picture. That's what she points at. That's how she asks for a story again. For something I thought of as an audio-first app, the pictures turned out to matter an awful lot.

I ended up spending a lot of time getting those covers right, and I'm now pretty happy with how they turn out. They also give me something I hadn't really planned for: artwork from her own stories that I can use elsewhere in the app. It makes more of it feel like hers, with familiar characters and pictures rather than the same imagery for everyone.

How the stories are turning out

The stories aren't going to win any awards just yet, but I've been pleasantly surprised by how well they turn out. Even in the last three months, I've noticed a lot of improvement in the models' ability to tell a story. I'm still waiting for one that genuinely makes me laugh out loud, though.

One tip that makes it more entertaining for the parents: add your adult friends as the gentle baddies. My daughter now goes to sleep hearing about the pretend misbehaviour of Mungo, Matt and Andrew most nights.

Having people you know turn up in the story adds something that another invented villain doesn't. The mischief stays gentle, but the familiar names make it more fun for the person listening along too.

Getting the phone out of the way

We still read our books together. Namesake fits into the audio part afterwards, when the lights are off and the story carries on.

The phone screen can be off while it plays. A Bluetooth speaker works too. I've also spent a surprising amount of the project on getting stories to the devices families already have: Alexa, Google Nest, Yoto and Creative Tonies.

Those connections have their own setup, and I'm still testing them as part of the beta. But getting a new story onto a Creative Tonie brings it back to the little box that helped start this in the first place.

You use a screen to make and choose the stories. Once they're playing, there's no reason for your child to keep looking at it. No ads in the stories, no streak to maintain, no next video waiting.

The question about AI

Some parents hesitate as soon as I say how the stories are made. I understand that. If something is going to play to your child in the dark, you should want to know what it is.

You can read the full story and its summary, edit it, and approve it before it's added to the shelf. Your child isn't chatting to an AI. The story text is written before you approve it; narration is then made from that text.

I also don't want to assume that a tired parent will inspect every word of every story forever. The way stories are written matters too.

The writing instructions vary with age: vocabulary, pacing, how much trouble the characters get into, and what sort of trouble it is. For younger children, baddies should be silly rather than frightening. Different story structures, openings and endings help keep each evening from becoming the same plot with different nouns.

There are rules about how stories finish, too. The trouble needs to be resolved. No cliffhangers at bedtime. And resolving the story doesn't mean every adventure has to end with everyone yawning and going to bed; sometimes the right last line is a joke.

Those are instructions for the writing, not a guarantee that generated stories will always get everything right. That's why the parent's chance to review and change them stays part of the process.

Where it is now

Namesake is an iPhone and Android app being tested with families ahead of a public launch. It has grown from that bedside workaround into a library of personalised, illustrated audio stories, with a choice of narrators and stories in different languages.

I'm still working on the same two things: making the story should be a nice part of the evening, something you can do together; playing it should take very little effort.

If you'd like to try it with your family, you can find Namesake at trynamesake.com.

I started because my daughter had a very particular story in mind and I wanted it to keep going after the lights went off. That's still a pretty good brief. Hopefully you'll like it if you give it a try.

← Back to the blog