Lesson 37 of 2116
Building With v0, Lovable, and Bolt (Fast App Prototyping)
AI app builders turn a prompt into a running app in minutes. Learn the strengths, the ceilings, and the moment you should eject to a real IDE.
Lesson map
What this lesson covers
Learning path
The main moves in order
- 1Prompt to Running App
- 2v0.dev
- 3Lovable
- 4Bolt.new
Concept cluster
Terms to connect while reading
Section 1
Prompt to Running App
v0, Lovable, and Bolt let you type a sentence and get a running web app in the browser within minutes. They solve the blank-file problem better than any tool before them. They are also capped in ways you should understand before you bet a startup on one.
Who they are in 2026
Compare the options
| Tool | By | Strength | Limit |
|---|---|---|---|
| v0.dev | Vercel | Polished React + Tailwind UI, Figma import, deploys to Vercel | Frontend only — no backend, DB, or auth |
| Lovable | Lovable AI | Full-stack via Supabase, SOC 2 / ISO / GDPR compliant | Prescribed stack — Supabase + React |
| Bolt.new | StackBlitz | Runs code live as it generates; React, Vue, Svelte, Next, Remix, Expo | Less polished UI defaults than v0 |
What they are great at
- Founder demos that need a working click-through in an afternoon
- Landing pages with interactive elements for marketing tests
- Internal tools that would otherwise die in the backlog
- Hackathon MVPs where speed trumps everything
- Designer-led prototypes that real code can be forked from
The prompt that actually works
Scope, screens, schema, style, auth — a prompt specific enough to get a working app, not a demo.
Build a dashboard for a small coffee shop to track daily sales.
Screens:
- Dashboard: today's revenue, top 3 drinks, chart of last 7 days.
- New Sale: pick a drink, enter quantity, submit.
- History: searchable/sortable table of all sales.
Data:
- Store sales in Supabase. Schema: id, drink_name, quantity, total_cents, created_at.
- Pre-seed 20 realistic entries.
Style:
- Warm, espresso-inspired palette. Sans-serif. Mobile-first.
Auth: single shared password (ENV var COFFEE_PASSWORD).When to eject
- You need tests and CI pipelines
- You need a stack the builder doesn't support (Django, Rails, Go services)
- You need complex auth, compliance, or data residency
- Your codebase is larger than 20k lines and regeneration is destroying context
- You want to own the infrastructure, not rent the builder's platform
A production-readiness checklist
- 1Can I export the full source to GitHub, with history?
- 2Does the generated code run locally without the builder?
- 3Can I deploy to a host I control, not just the builder's?
- 4Is auth real (JWT, sessions) or demo-grade (shared password)?
- 5Are there tests, or will I write them after ejecting?
- 6Is the database schema versioned and migratable?
Workflow: builder to IDE to production
The healthiest pattern we have seen: prototype in v0, Lovable, or Bolt, export to GitHub once the idea is validated, and continue in Cursor or Claude Code with real tests. The builder gets you past the blank file; the IDE gets you to production.
“Builders are the fastest way from idea to URL. They are not the fastest way from URL to scale.”
The big idea: AI app builders collapse the zero-to-one distance. Use them for prototypes, ship them for light production, eject when the weight of your project exceeds their ceiling.
End-of-lesson quiz
Check what stuck
15 questions · Score saves to your progress.
Tutor
Curious about “Building With v0, Lovable, and Bolt (Fast App Prototyping)”?
Ask anything about this lesson. I’ll answer using just what you’re reading — short, friendly, grounded.
Progress saved locally in this browser. Sign in to sync across devices.
Related lessons
Keep going
Creators · 50 min
The Landscape: Copilot vs. Cursor vs. Windsurf vs. Claude Code
The AI coding tool market fragmented fast. Let's map the 2026 landscape honestly: who is for autocomplete, who is for agents, who wins on cost, and what the tradeoffs actually feel like.
Creators · 55 min
Red-Teaming Your AI-Generated Code
Agents ship working code that's also quietly insecure. Red-teaming means actively attacking your own code. Let's build the habits that catch real-world exploits before attackers do.
Creators · 50 min
AI-Assisted Code Review Workflows (for Teams)
Code review is the highest-leverage touchpoint in a team. Automating the noise with AI frees humans to focus on the irreducibly human parts. Let's design the workflow.
