After a decade away from development, I built a fully-featured Sound Scheduler app in just 15 hours using AI-assisted “Vibe Coding.” Here’s how I did it—and why you might want to try it too.
The Last Time I Coded…
It was over 10 years ago.
Back then, I built a page generator tool—yes, one of those tools that spammed search results before Google got smart. My second project was a Strata Management SaaS platform, which I eventually sold. After that? I stepped away from development entirely.
Life happened. Careers shifted. Priorities changed.
But recently, I found myself curious again. Not about returning to development as a career—but about tinkering. About seeing what’s possible now that AI is in the mix.
That’s when I stumbled on a term that caught my attention: Vibe Coding.
What Is Vibe Coding, Anyway?
If you haven’t heard the term, you’re not alone. “Vibe Coding” isn’t an official methodology—it’s a community-born phrase that describes a new way of building software:
Vibe Coding = Using AI assistants (like LLMs) to guide you through building an app, step-by-step, while you focus on the vision, not the syntax.
Think of it less like traditional programming and more like having a patient, expert pair-programmer who never gets tired, never judges your questions, and can explain complex concepts like you’re five (the famous ELI5 method).
You describe what you want. The AI helps you figure out how. You learn as you go. You ship faster.
Sounds too good to be true? I was skeptical too. So I decided to test it.
My 15-Hour Experiment
I started with a simple idea: a Sound Scheduler app. Something that lets you schedule audio to play at specific times—like a smart alarm clock with custom sounds, volume control, and backup features.
Nothing too ambitious. Just enough to be useful.
Here’s how the next 15 hours unfolded:
Days 1-2: Research & Learning (~5 hours)
- Scoured Google and Reddit for “Vibe Coding” tutorials
- Found a golden tip: “Ask the LLM to teach you using ELI5”
- Tried it with Qwen (a powerful open-source LLM)
- Got walked through: installing Git, setting up Cursor (an AI-powered code editor), initializing a Next.js project, deploying to Vercel
Days 3-4: Building & Iterating (~10 hours)
- Described my app idea to the LLM
- Got scaffold code, then refined it through ~30 iterations
- Added features one by one: alarms, custom sounds, IndexedDB storage, mobile optimization, PWA support
- Spent ~25-35% of time learning—reading docs, understanding React hooks, debugging TypeScript errors
- The rest? Prompting, testing, tweaking
Hour 15: Ship It
- Deployed to Vercel
- Tested on desktop and mobile
- Shared with a few friends for feedback
- Sound Scheduler was live: sound-scheduler.vercel.app
What I Built (In Case You’re Curious)
The Sound Scheduler isn’t just a toy project. It’s a genuinely useful app with:
✅ Multiple alarms with custom schedules (time + days)
✅ 6 built-in sounds + custom audio upload (URL or file)
✅ Volume control (0-10) with mute option
✅ 5 color themes + dark/light mode
✅ Export/Import backup functionality
✅ Browser notifications
✅ Mobile-optimized + PWA installable
✅ All data stored locally (privacy-first)
And yes—it actually works. No smoke and mirrors.
Why This Would’ve Taken Months the Old Way
Let’s be real: if I’d tried to build this from scratch the traditional way:
- I’d spend weeks re-learning React, TypeScript, and modern tooling
- I’d get stuck on Web Audio API implementation
- I’d debug IndexedDB issues for days
- I’d second-guess UI/UX decisions without a designer
- I’d lose momentum and probably abandon the project
With Vibe Coding?
- The AI handled the “how”—I focused on the “what”
- When I got stuck, I asked. Got an explanation. Moved on.
- I could read the generated code and understand it (mostly!)
- I shipped something functional in hours, not months
That’s the magic.
But Wait—Can You Really Code Without Knowing How?
Short answer: Yes, but with caveats.
Vibe Coding isn’t about replacing developers. It’s about augmenting curious builders.
You still need:
- A clear vision of what you’re building
- Patience to learn as you go
- Willingness to read error messages and ask follow-up questions
- Basic logic skills (if/then thinking goes a long way)
What you don’t need:
- Memorized syntax
- Years of framework experience
- Perfect architecture on day one
The AI fills the knowledge gaps. You provide the direction.
The Funny Part: I’m Not Becoming a Developer Again
Look, this was fun. Challenging. Rewarding.
But am I quitting my day job to become a full-time coder? Absolutely not.
This wasn’t about career pivoting. It was about:
- Proving to myself I could still build something
- Testing a new paradigm (Vibe Coding)
- Having fun in the process
Think of it like learning to bake bread during lockdown. You might make a decent loaf, but that doesn’t mean you’re opening a bakery.
I’m happy staying on the product/operations side. But now I know: if I ever have another idea I want to prototype? I’ve got a new superpower.
Try It Yourself
If you’re curious:
- Use the app: sound-scheduler.vercel.app
- View the code: github.com/mo-robert-bhimji/sound-scheduler
- Try Vibe Coding yourself: Install Cursor, pick an LLM, and start with “Explain like I’m 5 how to build a [your idea]”
You might be surprised what you can ship in a weekend.
Keywords:
vibe coding, AI-assisted development, no-code tools, Next.js tutorial, React app building, Qwen LLM, Cursor editor, indie hacking, side project ideas, learn to code with AI, sound scheduler app, PWA tutorial, IndexedDB tutorial, mobile web app, TypeScript for beginners