A Vibe Coding Podcast About What Happens After the Prompt
Vibe coding has made it possible for far more people to build software.
App Minded is a podcast about what they're actually building.
I interview people using AI to turn ideas into apps and products, including people who started with little or no traditional coding experience.
We talk about Claude, Cursor, Replit, Lovable, Codex and the rest of the rapidly changing AI development stack. But the interesting part isn't which tool someone used.
It's what happened when they tried to make something real.
What is vibe coding?
Vibe coding is a term commonly used for building software by describing what you want to AI and letting the AI generate or modify much of the code.
That can make software development feel radically different for someone who doesn't know a programming language.
Instead of writing every line yourself, you might say:
- Build this screen.
- Change how this works.
- Connect this to my database.
- Why is this button broken?
- Here's the error. Fix it.
That sounds simple.
Sometimes it is.
Then the AI changes something completely unrelated, breaks the feature that worked yesterday, misunderstands what you meant or confidently sends you in the wrong direction.
That's where the real learning starts.
What do vibe coders actually build?
The guests on App Minded aren't building tutorial projects just to demonstrate a tool.
They're building around real problems.
Jocelyn Greenlee couldn't find a practical plan for building a chicken coop, so she built Buildara. Give it photos of something you want to build and the app helps create a plan, measurements, materials, shopping information and instructions.
Kayla Orozco was sick of manually combining school-supply lists for her three children. She built School Supplied and had it in the App Store after eight and a half weeks.
Christina Moore entered a 48-hour Lovable hackathon with no coding background and built Swan Society around a problem she'd seen repeatedly in book clubs.
Deepti used her own experience with kidney disease and transplant recovery to help shape Nourishly, an app designed around the dietary decisions people recovering from chronic illness have to make.
Chiara Barden combined a lifelong interest in thrifting with AI and built an AI treasure-hunting app.
The interesting thing about these apps isn't that AI generated some of the code.
It's where the ideas came from.
Do vibe coders need technical skills?
The answer changes depending on what you're trying to build.
You can get surprisingly far without traditional coding skills.
Jocelyn describes the relationship as being something like a product manager while AI acts as the engineer. She tells it what she wants, sees what it produces, explains what's wrong and keeps iterating.
Her first viable version of Buildara took roughly two concentrated days.
But she is also clear about what happened next.
Things broke.
Prompts were misunderstood.
A change in one place could break something somewhere else.
She had to research technical concepts she didn't understand.
The process taught her how to communicate with the AI more precisely.
That's a theme across the podcast.
You don't necessarily learn to write code.
You start learning how software works.
The tools change quickly
Guests on App Minded have used:
- Claude and Claude Code
- Cursor
- Codex
- Replit
- Lovable
- Bolt
- Base44
- Vercel
- APIs and automation tools
There isn't a single winner.
And there probably won't be one permanent winner.
Barbora has experimented with Cursor, Codex and browser-based AI builders but prefers more controllable coding tools for production work.
Chiara splits her workflow between Claude and Replit. She uses Claude almost like a software-development team, assigning different perspectives such as security, UX and frontend development before taking the resulting instructions into Replit.
El deliberately built projects in different platforms because she wanted to understand where Lovable, Bolt and Replit differed.
The tools will change.
Knowing what you're trying to build matters longer.
Vibe coding isn't a magic button
The demos can make this process look absurdly easy.
Describe app. Wait. App appears.
The first few minutes really can feel like that.
The problem is that a convincing demo and a reliable product are different things.
El experienced this with her first pickleball app. The app worked, but user feedback revealed a more fundamental problem: people were comfortable arranging games through text messages and didn't particularly want another app.
No amount of better code fixes that.
Barbora built Xroad Studio into a product with paying customers, but her experience has also taught her to be careful about whose feature requests she follows.
Cynthia has reached the point where building is easy enough that the restraint matters. Having an idea doesn't mean she needs to build it that weekend.
Those are product decisions.
AI doesn't make them disappear.
Can a non-developer ship a real app?
Yes.
There are multiple examples among App Minded guests.
Kayla shipped to the iOS App Store.
Jocelyn shipped Buildara to the iOS App Store.
Other guests have launched web products, AI applications, beta products and commercial software.
What "non-technical" means also becomes fuzzy surprisingly quickly.
People start without coding experience. Then they build something.
Soon they're talking about databases, APIs, authentication, deployment and model selection.
They haven't necessarily become traditional programmers.
They've become people who understand enough technology to make things.
The build is only half the story
This may be the biggest theme emerging from my conversations with builders.
Making software has become dramatically easier.
Getting people to care hasn't.
Barbora had beta users before launch and found one of her earliest customers through a WhatsApp group.
El openly describes distribution as the part she hasn't cracked.
Cynthia can keep building apps, but now has to devote time to promoting the ones she already has.
The bottleneck is moving.
That means the next generation of successful AI builders won't just be good at prompting.
They'll need to understand problems, people, positioning, distribution and why someone would choose their product in the first place.
Why App Minded?
I started App Minded after going from a non-technical background to shipping apps myself.
I wanted to hear from the people doing this in the real world.
Not just the polished launch post.
How did the idea start?
What did they use?
What broke?
How did they get unstuck?
How long did it take?
Did anyone want the thing after they built it?
How did they find their first users?
Would they build it the same way again?
Those are the conversations you'll find here.
So yes, App Minded is a vibe coding podcast.
But it's really a podcast about what becomes possible when building software is no longer reserved for people who learned to code first.