The experiment
Inky began as improvised bedtime stories — told aloud, images pasted into a doc by hand. The question underneath was bigger than bedtime: what happens to a person’s imagination when the distance between I have an idea and here it is, illustrated and read aloud collapses to nothing? Inky removes that distance. You describe a world — any reader, any age, any genre — and it returns a fully illustrated, narrated story you can read along with, extend, and hand to someone else. The technology underneath is real and deep. But it’s the instrument, not the point. The point is what people make when making is effortless.
The frontier it pushes
Imagination — the inner frontier. Most tools make existing work faster. Inky pushes on a harder question: when creation costs nothing, does a person imagine more — or just consume whatever the machine hands them? We’re building for the first: tools where the human stays the author and the machine stays the instrument.
What we’re learning
When the tool gets out of the way, the instinct to co-author is strong — people don’t want a finished story handed to them, they want their story made real. Generation was never the hard part. Keeping the human in the driver’s seat as the machine grows more capable is. That tension — capability versus authorship — is the experiment.
The instrument
- Multi-stage Gemini + Imagen 4 generation pipeline
- Native iOS app with word-level read-along narration
- Reader-agnostic worldbuilding with AI author configs
- Global community story library
- Dual monetization: RevenueCat (iOS) + Stripe (web)
- Firebase backend with real-time generation progress