Non-technical founder, vibe coded my first iOS app, it's now live on the App Store
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.
Shipping the app before fully understanding the codebase is exactly where structural diagnosis helps. I built a 15-minute repo audit for that moment. Happy to send the OpenClaw sample if useful.
Congrats on shipping! This is motivating but also terrifying me a bit. I'm a non-technical dad vibecoding @getkeptapp with Claude and just hit the "PWA vs App Store" wall hard. Claude is pushing PWA first ("grow to 1000 users, then decide on the cut and review pain").
For those who went straight to App Store early, was the exposure worth the review stress and 30% cut at low user numbers? Or did you regret not starting with PWA? Especially interested in how push notifications for reminders worked out.
congrats on shipping - the app store review gauntlet for a first launch is brutal and you made it through.
one thing that hasn't come up yet: for a parenting app with this specific use case, apple search ads is probably your best first paid channel to test. parents searching "bedtime story app" or "kids story app" are already problem-aware and actively shopping, so the intent-driven traffic converts at a completely different rate than cold meta audiences. you can get clean signal on whether $4.99/mo converts with just $30-50/day, and you don't need polished creative to start.
the subscription concern is really a retention question in disguise. bedtime story apps can actually support strong subscriptions if the daily habit forms - nightly use is a very different pattern than weekly use. if parents are opening it 5+ nights a week in week 1, that's a strong signal the price point will hold. if it's more sporadic, that's a different problem to solve first.
are you seeing any patterns in how frequently your early users are coming back, or is it still too early to have enough sessions to read?
Shipping without a technical background takes courage.
The interesting part here isn’t the bedtime stories — it’s that vibe coding lowered the barrier enough for you to move from idea to App Store.
Curious: at what point do you think a solo non-technical founder needs to transition from “it works” to deeper architectural understanding?
Love this! The "vibe coding" approach is so underrated - you proved that understanding every line isn't as important as understanding the problem you're solving.
The bedtime story exhaustion is such a universal parent pain point. I've seen founders overthink validation when they've already lived the problem daily.
For the audio quality issues, you might want to try switching between different OpenAI TTS voices or experiment with the speed parameter. Sometimes "alloy" or "echo" work better for storytelling than the default. Also, breaking longer stories into smaller chunks can help with consistency.
Curious - how are you handling the personalization beyond just the child's name? Are you storing any preferences or is each story completely fresh?
Shipping is the hardest part. Everything else is just iteration. Congrats on getting it live!
This is a great example of solving your own problem. The "one more story" exhaustion is so real — my friends with kids describe that exact 9pm creative bankruptcy.
Honest question about the subscription model though: parents are one of the most price-sensitive demographics for app subscriptions. They'll pay for stuff their kids use daily (YouTube Kids, educational apps), but bedtime stories might be a trickier sell because the usage window is so narrow — maybe 10 minutes a day, and only for a few years per kid.
Have you thought about a lifetime purchase option? For a niche parenting tool, I've seen that convert way better than subscriptions. Something like $19.99 lifetime vs $4.99/mo. Parents hate recurring charges for kids' apps specifically because they know the kid will outgrow it. A one-time buy removes that objection entirely.
On the audio quality — if you're using OpenAI's TTS, the newer models (tts-1-hd) are significantly better for narrative content. But honestly for a storytelling app, ElevenLabs might be worth the extra cost per generation. The expressiveness difference is night and day for children's content.
Also, the feature requests you're getting (more languages, story continuation, voice cloning) are interesting signals. I'd focus on story continuation first — that's the retention hook. If the kid wants to hear what happens next to the same character tomorrow night, you've basically built a habit loop.
congrats on shipping!! the hardest part of building an ios app is genuinely just getting through app store review for the first time lol. once you survive that everything else feels manageable
im also a solo dev building ios apps and honestly vibe coding has been a game changer. ive got 3 apps live right now - a daily cryptic crossword puzzle (wordplay), an ai horoscope podcast app (astrologica), and an article-to-audio converter (speakeasy). all built with ai assistance
what was the biggest surprise going from idea to app store? for me it was realizing that building the app is maybe 30% of the work. the other 70% is screenshots, descriptions, keywords, getting that first review, figuring out subscriptions vs one-time purchase...
also curious what stack you used? swiftui + ai coding or did you go the react native / flutter route?
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?