Ask anyone who has watched a five-year-old use a tablet what makes a story app good, and the answers tend to cluster around a handful of beliefs. They feel sensible. They sound like something a design team would agree on in the first meeting. Then the playtest happens, and the beliefs fall apart in ways that are hard to argue with once you have seen them.
The belief that a good story is enough
The reasoning goes that children already love stories, so a well-written narrative with a few pictures will hold attention on its own. It will not. A story app is not a book with a screen attached, and it is not a film either. The moment a child realises they can touch something, the passive version of the experience stops registering. What holds them is the sense that the story is responding to them specifically.
This is where branching narratives earn their keep, and where a linear story with a tap-to-advance button quietly fails. The child is not being entertained by the plot. They are being entertained by the discovery that their choice changed something. Take that away and you have a picture book that happens to be expensive to build.
The belief that more choice means more engagement
The opposite error is just as common. If some choice is good, the thinking goes, a lot of choice must be better. Give the child a fork in the road every few screens and the experience becomes richer.
In practice, young children often stall at a decision they did not expect. Too many branches, or branches that look and feel similar, produce hesitation rather than delight. The narrative structure has to be legible to someone who cannot yet read well, which usually means fewer, clearer moments where the story genuinely turns. A choice that leads somewhere visibly different is worth more than five that lead to the same place with different wording.
The belief that emotional learning can be bolted on
Many products in this space describe themselves as teaching empathy or emotional vocabulary. Some of them mean it. Others have attached a feelings quiz to the end of a story and called it a framework.
The difference shows up in whether the emotion is part of the plot or an overlay on top of it. A character who is frightened, and whose fear changes what happens next, teaches something a labelled face on a card cannot. This is the part that usually needs input from people who work with children, not just from people who build software, and it is the part most likely to get cut when a schedule tightens.
The belief that parental controls are a compliance detail
Founders often treat the parent-facing side as paperwork: a settings screen, a time limit, done. But parents are the ones deciding whether the app stays installed, and their concerns are not really about features.
What they want to know is whether the content is safe, whether the time spent is doing anything useful, and whether they can see that without sitting next to the child every session. An app that answers those questions earns a place on the home screen. One that hides the answers behind a menu loses it. The controls are not a gate at the end of the build; they are part of the reason a family keeps using the product at all.
Each of these beliefs is cheap to hold and expensive to discover in testing. The gap between what adults assume about children's apps and what children actually do with them is where the real design work sits.
The full write-up of how My Best Mood was approached, from child psychology research through branching narrative architecture and kid-tested playtesting, is on the My Best Mood interactive storytelling case study.
Top comments (0)