Vibe coding: the complete guide to building apps by talking to AI
Read in : Français

Contents
- What is vibe coding, in one sentence?
- Two ways to vibe code
- How does vibe coding actually work?
- Which tools can you use for vibe coding?
- What can you build with vibe coding, and what should you avoid?
- What works well
- The decision tree before you start
- A 7-step method to build your first app
- 1. Write down what you want before you open the tool
- 2. Write a scoped first prompt
- 3. Approve the plan, then build in small pieces
- 4. Save every version that works
- 5. Test like a rushed, clumsy user
- 6. Check security before you invite anyone
- 7. Deploy and watch the costs
- The numbers to know before you start
- The real risks of vibe coding
- Exposed data
- Keys and bills
- The endless loop
- Technical debt
- Do you need to know how to code to vibe code?
- Vibe coding, AI-assisted development, agentic engineering: where do things stand in 2026?
- The beginner vibe coder's checklist
- Frequently asked questions
- Frequently asked questions
- Sources
Vibe coding is building an app by talking to an AI: you describe what you want in plain English, the tool writes the code, you test it, and you fix problems by rephrasing. The term was coined in February 2025, and by 2026 it has become a real way to build prototypes, internal tools and small products. This guide gives you the definition, the tools, a step-by-step method, verified numbers and the traps that get expensive.
What is vibe coding, in one sentence?
Vibe coding is a way of programming where you guide an AI in natural language instead of writing the code yourself. AI researcher Andrej Karpathy, a co-founder of OpenAI, coined the term on February 2, 2025, in a post on X.
There's a new kind of coding I call "vibe coding", where you fully give in to the vibes, embrace exponentials, and forget that the code even exists.
— Andrej Karpathy, X
In the same post, Karpathy said the approach was "not too bad for throwaway weekend projects." The phrase then spread everywhere: Collins Dictionary named it its 2025 Word of the Year and defined it as "the use of artificial intelligence prompted by a natural language to assist with the writing of computer code."
For the full story of the term and the different ways people use it, read what vibe coding means and where it came from.
Two ways to vibe code
Google Cloud separates two practices, and the distinction will come back throughout this guide:
- "Pure" vibe coding: you trust what the AI produces without reading the code. Great for exploring an idea or hacking together a personal tool.
- Responsible AI-assisted development: the AI does most of the work, but someone reviews, tests and understands what ships.
Most serious projects start in the first box and need to end up in the second. We map the boundary in vibe coding vs AI-assisted development.
How does vibe coding actually work?
Vibe coding runs on a short loop: describe, generate, test, fix. You repeat it until the thing works.
- Describe: you write in everyday language what you want ("a sign-up form with email and password").
- Generate: the tool writes the code, often the interface, the logic and the database in one go.
- Test: you click around, fill things in, try to break it.
- Fix: you describe what's wrong, paste the error message, and the AI corrects it.
Recent tools add a step before generation: a plan mode where the AI proposes what it will do before touching the code. Bolt's documentation describes its Plan Mode as a way to "plan and ask questions without making changes to your code." Lovable also recommends asking the AI to raise its questions before it starts coding.
Which tools can you use for vibe coding?
Vibe coding tools fall into three families, depending on your skills and what you want to build. The right choice has less to do with "the most powerful tool" than with whether you want to see the code at all.
| Family | Examples | Do you see the code? | Best for | Typical projects |
|---|---|---|---|---|
| Browser-based app builders | Lovable, Bolt, Replit, v0, Base44 | If you want to, but you don't have to | Beginners, founders, designers | Prototypes, MVPs, small SaaS, internal tools |
| AI code editors | Cursor, Windsurf, GitHub Copilot | Yes, you work in the files | People comfortable with a code project | Growing an app, taking over a project |
| Command-line agents | Claude Code, Codex | Yes, in your terminal or editor | People comfortable with a terminal | Long tasks, big projects, automation |
| Big-tech platforms | Google AI Studio, Firebase Studio | Depends on the tool | The curious, Google developers | Fast prototypes with Gemini models |
A few reference points from the official docs:
- Lovable generates both front end and back end. Its built-in backend, Lovable Cloud, provides a database, authentication, storage and functions, and according to the docs "utilizes Supabase's open-source foundation."
- Replit sets up the project, creates the application, checks its work and fixes problems along the way. Its docs say the agent creates checkpoints "so you can roll back to any previous state."
- Bolt offers its own database, publishing to a live site and custom domains.
For a tool-by-tool breakdown, see the complete comparison of vibe coding tools, then Lovable vs Bolt vs Replit if you're starting out, or Cursor vs Claude Code vs Codex if you want real code.
What can you build with vibe coding, and what should you avoid?
Vibe coding shines on projects where mistakes are cheap and you can test every screen yourself. It gets risky as soon as personal data, money or legal obligations are involved.
What works well
- A clickable prototype to validate an idea with customers.
- An internal tool that replaces a spreadsheet (inventory, scheduling, quotes).
- A landing page, a simple business website, a small game.
- Scripts and extensions that automate a repetitive task.
You'll find detailed examples in 25 real vibe coding use cases, including replacing a spreadsheet with a real app and building a SaaS up to the first paying customer.
The decision tree before you start
- If the app is just for you or your team, with no sensitive data, then go pure vibe coding and iterate fast.
- If strangers will create accounts, then plan a real security check (authentication, database access rules) before launch.
- If you take money, then use an established payment provider and never store card data yourself.
- If the app handles health, banking or children's data, then have a developer review it before it goes live.
- If the app needs to last for years with a team, then plan to move to a code editor and a more structured method such as spec-driven development.
A 7-step method to build your first app
A successful vibe-coded app starts with a written scope, moves forward in small steps and ends with testing. Here's the sequence that avoids most disasters.
1. Write down what you want before you open the tool
One page is enough: who it's for, what problem it solves, the 3 to 5 must-have features, and what's out of scope. Lovable suggests answering four questions first: what the product is, who it's for, why they'll use it, and the one key action they should take. We show you how in writing a PRD your AI builder understands.
2. Write a scoped first prompt
Here's a template to copy and adapt:
I want to build a booking web app for a hair salon.
Users: customers (book appointments) and the owner (sees the schedule).
Features for the first version:
1. The customer picks a service, a day and a free time slot.
2. The customer sees a confirmation on screen.
3. The owner sees today's appointments and can cancel one.
Out of scope for now: online payment, SMS reminders.
Style: clean, easy to read on a phone.
Before writing code, ask me any questions you need answered, then propose a plan.
The full method, with more examples, is in vibe coding prompts: a 5-step method.
3. Approve the plan, then build in small pieces
Don't ask for the whole app at once. Bolt's documentation says to "ask Bolt to make one change at a time" and check it works before moving on. Lovable says the same thing: one meaningful change at a time, then look at the result.
4. Save every version that works
When a step works, save it. App builders keep a version history or checkpoints. With an editor or an agent, use Git: Git for vibe coders covers the bare minimum so you never lose a working version.
5. Test like a rushed, clumsy user
Fill in forms with nonsense, open the app on your phone, log out, come back. Testing AI-generated code when you're not a developer gives you a simple routine.
6. Check security before you invite anyone
This is the step everyone skips, and the one that makes headlines. Run through the pre-launch security checklist, especially Supabase RLS rules and where your API keys live.
7. Deploy and watch the costs
Pick hosting that fits (Vercel, Netlify or shared hosting) and estimate what the app will cost each month in credits, API calls and hosting: the real cost of a vibe-coded app.
The numbers to know before you start
Published studies paint a nuanced picture: vibe coding speeds up the start of a project, but code quality and security still need watching.
| Figure | What it says | Source |
|---|---|---|
| 25% | Share of Y Combinator's Winter 2025 startups whose codebases are about 95% AI-generated | TechCrunch, March 2025 |
| 72% | Share of developers surveyed by Stack Overflow who say vibe coding is not part of their professional work | Stack Overflow, 2025 survey |
| 66% | Share of developers who say they spend more time fixing "almost-right" AI code | Stack Overflow, 2025 survey |
| 19% | Slowdown measured in 16 experienced developers using AI on their own projects, while they believed they were faster | METR, July 2025 |
| 45% | Share of tests where AI-generated code introduced a security flaw, across more than 100 models | Veracode, 2025 |
| 170 of 1,645 | Lovable-built apps showcased on its site that let anyone access their users' data | Semafor, May 2025 |
Two important caveats. The YC 95% figure is about founders whom YC managing partner Jared Friedman describes as "highly technical" and "completely capable of building their own products from scratch." And METR says its study covers one specific setting (experts on projects they know inside out) and doesn't generalize to all software work.
The real risks of vibe coding
The real risk isn't "the AI writes bad code." It's "nobody checks what goes live." These are the ones that come up most.
Exposed data
In the Lovable case reported by Semafor, the flaws came from misconfigured Supabase databases: names, email addresses, financial information and API keys were reachable. The issue was flagged by Matt Palmer, a Replit employee, and made public in the US National Vulnerability Database. The lesson: an app that "works" can still leave the door wide open.
Keys and bills
An AI API key pasted into browser code can be grabbed by anyone, who will then spend your credit. It's the easiest mistake to avoid: the key stays on the server, never in the front end.
The endless loop
The AI fixes one bug and creates two. In his original post, Karpathy admitted he sometimes worked around a bug or asked "for random changes until it goes away." For a throwaway project, fine. For a project that matters, you need a debugging method and saved versions. The usual suspects are listed in 12 mistakes that sink vibe coding projects.
Technical debt
The more a project grows without a plan, the more every change breaks something else. The fix: a living spec, small steps, and moving to a tool that shows you the code once the project gets serious.
Do you need to know how to code to vibe code?
No, you can build a first app without ever having written a line of code. But a few concepts make a huge difference: what a database is, the difference between front end and back end, what an API key is, and how to read an error message. We sort out what matters in can you vibe code without knowing how to code?.
Developer Simon Willison puts the limit well. His golden rule for production code: he won't commit any code he couldn't explain exactly to somebody else. You don't need that bar for a personal tool. You do need it once other people trust your app with their data.
Vibe coding, AI-assisted development, agentic engineering: where do things stand in 2026?
In 2026, the vocabulary is moving as fast as the tools. Three terms coexist:
- Vibe coding: you don't read the code, you judge by the result. That's Simon Willison's strict definition: building software with an LLM "without reviewing the code it writes."
- AI-assisted development: the AI writes, a human reviews, tests and takes responsibility.
- Agentic engineering: the term Karpathy said he preferred in February 2026 for professional work with coding agents, because there is "an art & science and expertise to it."
The line is blurring. In May 2026, Simon Willison wrote that the two practices had started to blur in his own work, as agents became reliable enough that he no longer reviewed every line. For you, the takeaway is simple: the more autonomous the tool, the more your tests and your security checklist matter.
The beginner vibe coder's checklist
Before you show your app to anyone, check these points:
- I've written one page on what the app does and doesn't do.
- I built it feature by feature, testing after each step.
- I have a saved version that works.
- No API key is visible in the browser code.
- A user can't see another user's data.
- I've tested the app on a phone and with nonsense inputs.
- I know the monthly cost of the app at 10, 100 and 1,000 users.
Frequently asked questions
Frequently asked questions
Is vibe coding free?
You can start vibe coding for free: most app builders have a free plan with a limited number of messages or credits. For a real project, you'll usually end up paying for a subscription, then hosting, the database and any API calls. We cover what you can do without paying in the free vibe coding guide, and the real costs in what a vibe-coded app really costs.
Which tool should a beginner use for vibe coding?
If you've never coded, a browser-based app builder such as Lovable, Bolt or Replit is the easiest place to start: everything is built in, from the interface to publishing. If you're already comfortable with a terminal or a code editor, Cursor, Claude Code or Codex give you more control. The best choice depends on your project, not on this month's rankings.
Can a vibe-coded app go to production?
Yes, a vibe-coded app can go to production, but not as is. Before real users arrive, you need to check authentication, database access rules, where your API keys live, backups and costs. For an app that handles money or sensitive data, a review by a developer is still the best insurance you can buy.
Will vibe coding replace developers?
Nothing in the published data points that way so far. Stack Overflow's 2025 survey shows that most developers don't use vibe coding in their professional work, and that many spend time fixing AI code that is almost right. Vibe coding mainly widens the number of people who can build a tool, and shifts developers' work toward more review and architecture.
How long does it take to build an app with vibe coding?
A simple prototype can be ready in an afternoon, because the AI generates the interface and basic logic very quickly. The time goes into the details afterwards: edge cases, bugs, security, deployment. For an app real users will rely on, expect several days or weeks, especially if you're learning the basics along the way.
Sources
- Andrej Karpathy's original vibe coding post — X
- Vibe coding named word of the year by Collins Dictionary — Euronews
- What is vibe coding? — Google Cloud
- Not all AI-assisted programming is vibe coding (but vibe coding rocks) — Simon Willison
- Vibe coding and agentic engineering are getting closer than I'd like — Simon Willison
- OpenAI co-founder says agentic engineering is the next big thing in AI coding — Digit
- A quarter of startups in YC's current cohort have codebases that are almost entirely AI-generated — TechCrunch
- Developers remain willing but reluctant to use AI: the 2025 Developer Survey results — Stack Overflow
- Measuring the impact of early-2025 AI on experienced open-source developer productivity — METR
- 2025 GenAI Code Security Report — Veracode
- The hottest new vibe coding startup Lovable is a sitting duck for hackers — Semafor
- Prompting best practices — Lovable Docs
- Lovable Cloud — Lovable Docs
- Plan Mode — Bolt Support
- Replit Agent — Replit Docs


