I spent four months blaming my users for a bug in my onboarding
For four months I had a clean explanation for why half my users vanished after install. It was completely wrong.
An AI dream interpreter, built end-to-end through an AI pipeline — zero lines of code written by hand.
Dreambook was the testing ground. I wanted to find out what an AI-driven pipeline could actually carry — architecture, content, ASO, monetization — with one person making decisions and the AI doing the execution. So I picked a real consumer product and shipped it to the stores to find out where the method holds and where it breaks.
The premise was simple and a little uncomfortable: if AI can handle the execution layer, what does a solo founder actually do? My answer, after building this: you make decisions, set quality bars, and debug the places where the AI confidently goes in the wrong direction. That’s the job. Not writing code. Not producing content. Deciding, evaluating, correcting.
Everything in Dreambook was built through that pipeline. The Flutter app, the FastAPI backend, the LLM interpretation chain, the S3 content engine, the ASO copy, the onboarding flow, the monetization setup. One person, end to end, shipped to both stores and first paying customers.
Screenshots and metrics — coming in Phase 6.
Engineering breakdowns from building Dreambook.
For four months I had a clean explanation for why half my users vanished after install. It was completely wrong.
Want to see the product itself?
Best on desktop. This site has a richer, motion-driven experience — open it on a computer for the full effect.