What Happens When AI Builds Your App for You?
I set out to build a simple app for kids. Nothing overly complex. Just an idea:
“Backyard Coding Adventures”
An app that generates fun outdoor coding challenges based on age.
But instead of writing the code myself… I decided to try something different. I tested what people are calling vibe coding. Instead of coding line by line, you guide AI using natural language and let it build for you. What happened next surprised me.
The Experiment
I used the same idea and prompt across four different AI tools:
- Base44 (free version)
- Google AI (Gemini Pro)
- Replit (developer-style environment)
- Bolt (fast-response builder)
Same input. Very different results.
What I Noticed Right Away
Each tool had a completely different feel:
- One was fast and almost instant
- One felt more structured and deliberate
- One felt like collaboration
- One was quick… but the output was just okay
This alone was eye-opening. Not all AI tools behave the same.
Understanding Tokens (Why Everything Suddenly Stops)
At some point in almost every tool… I hit a limit. I ran out of tokens.
If you’re new to this idea, tokens are essentially how AI tools measure usage.
Every prompt and response uses tokens, and once you reach your limit, the system stops responding.
This is especially important if you’re using free tiers. You may be just getting into a flow… and suddenly you’re done. That constraint changes how you approach building.
The Mindset Shift (This One Surprised Me)
I started this experiment trying to just vibe with the tools.
Explore.
Try things.
See what happens.
But then something shifted.
My developer mindset kicked in.
I found myself focusing on:
- structure
- layout
- usability
- getting things “right”
I even felt a bit of anxiety trying to refine what the AI was producing.
That pulled me out of the creative flow.
And it made me realize something important…
A younger learner might approach this completely differently.
They might just explore.
And that might actually be the better way to start.
An Unexpected Connection to Interface Design
Because I teach interface design, I naturally started evaluating what the tools were producing.
I kept coming back to core principles:
- clarity
- alignment
- usability
- simplicity
In many cases, the generated interfaces needed refinement. Interestingly, some suggestions from the tools felt like they may have been influenced by patterns seen in other applications. That raised an important question:
👉 Are these tools helping us design… or guiding us toward what already exists?
The Bigger Takeaway
This experiment wasn’t just about tools. It revealed something bigger. We are not just improving how we code. We are changing how we build.
Some tools prioritize:
- speed
- creativity
- exploration
Others lean toward:
- structure
- control
- refinement
And every tool comes with limits.
How to Get Started with Vibe Coding
If you’re curious about trying this yourself, here’s a simple way to begin:
Start with a small idea
Use plain language
Let the AI generate something
Then iterate and refine
But most importantly…
👉 Have a plan
Especially if you’re using free tools, because token limits come quickly.
Final Thoughts
Vibe coding is real. It lowers the barrier to building in a way we haven’t seen before. But it doesn’t remove the need for thinking.
You still need to guide the process.
Evaluate what’s created.
And decide what “good” looks like.
The tools can build quickly. But how you build still matters.
Try This
Take 10 minutes this week and try building something simple using one of these tools.
Don’t overthink it.
Just start.
You might be surprised what you create.
🔁 Keep Exploring
If you enjoyed this episode, be sure to:
- Subscribe to Mr. Fred’s Tech Talks
- Share this episode with someone curious about AI
- Explore more at https://www.getmecoding.com
