I don't have a tech background. Never built an iOS app. But my kid kept asking for "one more story" at bedtime and I was out of ideas by 9pm. So I built an app to solve it.
The app:
Gramms — generates personalized bedtime stories. You enter your child's name, pick a theme, it creates a unique story with AI narration. Like a grandparent reading to them.
How I built it:
Vibe coded the entire thing. Claude did most of the heavy lifting. I'd describe what I wanted, it would write the code, I'd test, break things, describe the bug, repeat. Took a few months of evenings and weekends.
I don't fully understand half of what's in the codebase. But it works and it's live.
Honest status:
Just launched, almost no users yet
Monetization is a subscription but I haven't validated if parents will pay
Audio quality is inconsistent (OpenAI issue I'm still debugging)
Already getting feedback: people want more languages, story continuation, voice cloning
The ask:
If you're a parent with young kids, I'd genuinely love you to try it and tell me what's broken. First app I've ever shipped — early feedback matters a lot.
If you're not a parent but know someone who is — would appreciate you sharing this with them.
https://apps.apple.com/in/app/gramms-bedtime-stories/id6758451330
What's your experience vibe coding a full product to launch? Curious if others are shipping real apps this way.
Congrats on shipping! As a solo builder myself, I know how much momentum it takes to go from idea to App Store.
The vibe coding approach is interesting — you basically described a feedback loop with AI: describe intent, get code, test, describe bug, repeat. That is honestly a valid development workflow when the scope is focused. The fact that you shipped a real product that real people can use matters more than understanding every line.
For the audio quality issue — you might look into ElevenLabs as an alternative to OpenAI TTS. I have been experimenting with different voice synthesis engines and ElevenLabs tends to be more expressive for storytelling-style narration. Worth comparing.
Curious: how did you handle state management and data persistence in the app? That is usually where vibe-coded projects hit their first scalability wall.
The bedtime story angle is clever - parents definitely have that "out of ideas by 9pm" pain point. Getting those first parent users to stick will tell you everything about product-market fit.
Congrats on launch!
The feedback you are getting, is what I often see. The core idea works but there is much evolving happening.
What of these requests feel most important right now? expanding features or stabilizing audio quality?