The child reads out loud, and the page answers.
Every read-along app I could find narrates to the child. This one listens. The reader says the words, and the illustration moves as they land.
The inversion.
A read-along app that reads aloud to a child is a very good audiobook and a very bad reading tool. The child is a passenger. Nothing they do changes anything.
So this one never narrates. It waits. The scene only moves when the reader says the word, which makes the animation a reward for reading rather than a substitute for it. A child who stops reading gets a page that stops.
Nothing narrates. The reader is the narrator.
The scene responds word by word, so the pace belongs to the child.
It stops when they stop, which is the whole point.
Why it exists.
I did not build it as a product to sell on its own. I built it as the reason to pick the book up.
A picture book competes with every other picture book on price and cover. A picture book that does something none of the others do competes on a different axis. That is cheaper than buying attention and it lasts longer.
What is actually built.
There is a working prototype. The microphone path is the fragile part and it is the part I built first, because a demo that fails on the one thing it is claiming is worse than no demo.
Ask and I will walk you through it end to end.
What this proves
- I find the differentiator and build it, rather than buying ads for it.
- I build the risky part first, because that is where the project actually gets decided.
- I can tell the difference between a feature and a reason to buy.
Tell me what you are trying to finish.
The thing that makes someone choose you is rarely the thing on the feature list.
Send me the project that has been sitting there. I will tell you what I would do with it and whether I am the right person to do it.