How to vibe code your first app (this weekend, for real)
A Friday-to-Monday plan that ends with something live on the internet with your name on it. It will be small. That's the point.
The Vibers team4 min read
Most first apps die in the planning. Someone decides to build “Uber, but for dog walkers”, spends three evenings choosing a name and a logo, and quietly never opens the laptop again.
This plan is designed to stop that happening to you. It assumes no coding experience and about ten hours spread over a weekend. By Sunday night you’ll have a link you can send people.
Friday night: pick something embarrassingly small
Your first project should pass four tests:
- It solves a problem you personally had this week.
- You can describe it in one sentence without using the word “platform”.
- Nobody needs to log in.
- It doesn’t take anyone’s money.
Tests three and four aren’t about ambition. Logins and payments are where vibe coded projects get into trouble (we explain why in what is vibe coding), and you want your first win to be a clean one.
Some ideas that pass:
- A page that sorts your messy shopping list by supermarket aisle.
- A countdown for a friend’s wedding, with the dress code and a map.
- A holiday cost splitter that understands “but I didn’t drink”.
- A dinner picker that knows you hate mushrooms.
- A tracker for your five-a-side team’s goals, assists and excuses.
Some that don’t, yet: social networks, marketplaces, and anything you’d describe to an investor.
Friday night, part two: write the brief
Before you touch any tool, spend ten minutes in your notes app. This one page will save you hours.
I want to build: [one sentence] It’s for: [who, even if it’s just me] The main screen shows: [what you see when it opens] The one thing it must do well: [the job] It should feel like: [an app or a place you like] Leave out for now: logins, payments, settings, dark mode
The last line matters most. AI tools are eager to please. Ask for a dinner picker without limits and you’ll get a dinner picker with user accounts, a newsletter signup and a settings page you never wanted.
Saturday morning: choose a tool (and don’t overthink it)
Every one of these can get you to a finished first app. Pick the row that sounds like you and move on.
| If you… | Start with |
|---|---|
| Have never coded and want something on the web today | Lovable or Bolt |
| Care most about how it looks | v0 |
| Want it all in the browser, including a bit of backend | Replit |
| Already know your way around a code editor | Cursor |
| Are comfortable in a terminal | Claude Code |
Most of them have a free tier or a trial that’s enough for a first project. If you want the longer comparison, see the best vibe coding tools.
Saturday: the first prompt, and the loop
Paste in your brief, word for word. What comes back will be impressive and wrong. That’s normal. Now you’re in the loop: look at it, say what’s wrong, look again.
A few habits that separate a fun Saturday from a miserable one:
- One change per message. Five requests at once means five chances to break something, and no idea which one did.
- Say what you see, not what you think is wrong. “The total shows NaN after I delete a row” beats “the maths is broken”.
- Notice the third fix. If the AI has “fixed” the same bug three times, stop. Go back to the last version that worked (most tools have a history or checkpoints) and ask a different way.
- Ask for an explanation before a fix. It slows the AI down, and it often catches its own mistake.
Stop. Don’t write any code yet. We’ve tried to fix this three times. List the three most likely causes of this bug, how we could tell which one it is, and which you’d check first.
Saturday evening: make it look like yours
Left to itself, AI design has a look: purple gradient, rounded cards, an emoji in the heading. People recognise it instantly. You can do better with one sentence.
Adjectives like “modern” and “clean” get you the same look as everyone else. References get you something with character:
- “Make it feel like a railway timetable.”
- “Like a 1990s Mac, but readable.”
- “Like the menu of a nice neighbourhood café.”
- “Like a football sticker album.”
Sunday: put it on the internet
Most tools publish with a single button. Then do three things:
- Open it on your phone. Things that looked fine on a laptop break on a phone more often than not.
- Send it to one person and watch them use it. Don’t explain anything. Just watch where they hesitate.
- Fix only what they got stuck on. Not the five ideas you had while watching. Those are for next weekend.
If you want a proper address instead of the tool’s default link, a domain usually costs about the same as a takeaway for a year.
Monday: show it off
Post it on Vibers. Add the screenshots, the tools you used, an honest build time, and a few lines about how it went. The build story is what people actually read: the prompt that unlocked it, the bug that ate two hours, the moment it worked.
Small projects do well here. Nobody’s expecting a unicorn. They want to see what you made and how.
What to build next
For project two, add exactly one scary thing: saving data, or a login. Just one. You’ll learn more from that one step than from a whole new app.
And if you’d like someone else to choose for you, there’s always a vibe coding challenge running. A brief and a deadline do wonders for actually finishing things.