Vibe coding for complete beginners: your first app in a weekend

Most people who want to build an app are held back by the same two beliefs. First, that you need to learn a language (JavaScript, Python, Swift) before you start. Second, that "real" apps take months. Both were true in 2020. Neither is true in 2026.

This is the weekend plan. Total time: two days. Total cost: about fifteen quid. At the end you will have a real, live app — on the internet, with a URL your friends can visit — that you built without touching a line of code in anger.

What vibe coding actually means

Vibe coding is not "no-code". It is coding, but the coding part is done by AI. You describe what you want, the model writes the code, you review it, and you run it. When something breaks, you describe the bug, the model fixes it.

The skill you are practising is not syntax. It is:

• Specificity — saying exactly what you want
• Product taste — knowing when something looks or feels wrong
• Debugging intuition — noticing when the AI is hallucinating

You build those skills by shipping, not by reading. Which is why the weekend framework below starts building in hour one.

Friday evening (1 hour): pick a tiny, personal problem

Most beginners kill their first project by choosing something too big. "A Duolingo competitor." "A dating app for cyclists." "Airbnb for spare desks."

All fine ideas. None suitable for hour one.

Pick something smaller. Something you personally wish existed. Four examples that new builders have shipped in a weekend:

1. A dashboard that shows your next three trains and the weather at your destination
2. A splitwise replacement that tracks who owes what for one specific flatshare
3. A tool that turns your weekly gym notes into a progress chart
4. A private reading log where you rate books and it suggests the next one

Write yours in one sentence. "A tool that does X for Y." If you cannot write it that short, it is too big.

Friday night (2 hours): open Lovable and describe it

Lovable is the fastest way for a beginner to get to a working prototype. It handles setup, deployment and hosting, so you can focus on the idea.

Go to lovable.dev, create a free account and paste this prompt:

"Build me a web app called BookShelf. It is a private reading log. Users sign in with email. They can add a book with title, author, rating (1-5 stars) and a short review. The home page shows their books as a grid of cards with the cover if available from the Open Library API. There is a 'suggest next book' button that returns one random unread book from their to-read list. Use a soft cream background, rounded corners, and a single accent colour (forest green). Mobile-friendly."

Lovable will scaffold the entire app — frontend, database, auth, hosting — in about three minutes. You will see a preview on the right.

Try it. Add a book. See if it breaks.

Almost every first-time builder underestimates how fast this step is. You will have a working prototype of a real app before you finish your first cup of tea.

Saturday morning (2 hours): make it actually yours

The Lovable scaffold is generic. This is where your product taste starts mattering.

Open Lovable's chat and ask for specific changes, one at a time:

• "Change the 'Add book' button so it is a floating pill in the bottom right, not a header button."
• "When I hover over a book card, show a subtle shadow and a 'view details' overlay."
• "The star rating should be clickable stars, not a dropdown."
• "Add a 'Mark as read' toggle on each card."

One change per message. Test after each one. If something looks wrong, describe what you see and what you want instead.

This is the vibe coding loop:

1. Describe the change
2. See the change
3. Decide if you like it
4. Keep, refine or revert

You are training the habit of specificity.

Saturday afternoon (3 hours): switch to Claude Code for the harder bits

Lovable is brilliant for getting started. But somewhere around hour six you will hit a wall — something Lovable keeps misunderstanding, or a feature it cannot quite get right.

That is when you switch to Claude Code.

Connect Lovable to GitHub (one click), then clone the repo to your laptop. Open the folder in Claude Code. Now you have the same project, but with a much more capable AI that can hold the whole codebase in context.

Claude Code can:

• Refactor several files at once when you want to rename something
• Understand why a bug is happening by tracing calls across files
• Run tests, fix the failures and run them again
• Install new packages and wire them up

Prompt example:

"I want to add an Open Library ISBN lookup so users can type an ISBN and auto-fill title, author and cover. Add a second input on the Add Book screen. When the user types 10 or 13 digits, fetch from the Open Library API and populate the other fields. Keep the manual inputs as a fallback. Add error handling."

Claude Code will edit the component, add the fetch logic, handle edge cases and run through the changes with you.

Saturday evening (1 hour): deploy

If you started with Lovable, your app is already deployed to a Lovable URL. But if you want to own your launch, move it to Vercel.

Prompt:

"Guide me through deploying this to Vercel with a custom domain. I own bookshelfapp.co.uk. Walk me through each step."

Claude Code will give you the exact commands, help you set up the DNS, add the environment variables and make your app live. This is where things get real.

Pay for the domain (around £10/year at Namecheap or a UK registrar). Wait for DNS to propagate. Visit your URL. Feel genuinely different about what you are capable of.

Sunday morning (2 hours): get one real user

The single most important thing you can do on Sunday morning is get one person who is not you to use the app.

Text a friend. Post in a Discord. Put it on a WhatsApp group. Ask:

"I built a thing. Takes 2 minutes to try. Can you tell me what is confusing?"

Watch them use it if you can. Do not explain. Notice where they hesitate, misclick or give up. These are the only bug reports that matter.

Sunday afternoon (2 hours): fix the three most obvious things

Based on your friend's feedback, pick the three most obvious things and fix them with Claude Code.

Common first-user feedback:

• The sign-up flow is confusing
• The primary action is not obvious
• Something loads too slowly
• An error message is unhelpful

Pick three. Fix three. Do not try to rebuild everything.

Sunday night (30 minutes): publish what you made

Write one short post on LinkedIn, X, or Reddit's r/SideHustleUK:

"I built a private reading log this weekend with Claude Code and Lovable, deployed to Vercel. Total spend: £14. Link: bookshelfapp.co.uk. Would love feedback."

This is where most beginners flinch. Don't. You will get more useful replies from that single post than from another twenty hours of polishing.

Your week 2 options

By Monday morning you will be in one of three camps.

1. You love it. Keep shipping. Pick the next obvious feature. Get a second real user.
2. You are indifferent. Pick a different idea for next weekend. The skill transfers.
3. You hate it. Fine. You now know building is not for you — and you learned that in 48 hours instead of 6 months.

All three are wins.

The budget

Item	Cost
Lovable (free tier)	£0
Vercel (hobby tier)	£0
Domain	£10/year
Claude Code (starter)	£0-20
Optional Lovable Pro	£16/month
Total weekend spend	£10-50

Fewer than three weekday lunches.

Where to go next

Vibe coding is not a trick. It is the new default. The people who will ship the most interesting UK consumer products over the next five years are the ones who stop pretending they need a CS degree and just build the thing.

If you are looking for a specific weekend idea with validated UK demand, keyword data and a step-by-step builder prompt, the IdeaStack weekly report is free.

---

Get the weekly IdeaStack report — every Thursday we publish one deeply researched UK business opportunity with real keyword data, competitor analysis, SERP landscape, scoring frameworks and copy-paste builder prompts. Read the latest free report.