← All writing

How to vibe code your first app

Vibe coding means building an app by describing it to AI. How to pick a small first project, choose a tool, keep it working, and ship it in a weekend.

By Branislav · · 3 min read

Short answer: pick a tiny app you would use yourself, describe it to an AI builder one screen at a time, save a working version after every step, and put it online the same day. Most first projects fail because they are too big, not because the tools are not good enough.

What is vibe coding?

Vibe coding is building software by describing what you want in plain language and letting AI write the code. You steer, test and correct. The code is the AI's job, at least at first.

It works surprisingly well for small apps. It gets hard when the app grows and nobody, including you, understands how it fits together. The habits below are how people avoid that wall.

How do you pick a first project?

Small, personal, and finished in a weekend.

  • Good: a tracker for something you already track in a spreadsheet, a page that turns a form into a PDF, a tool for one annoying task at work.
  • Too big: a marketplace, a social network, anything with payments and logins and an admin panel on day one.

If you can describe the whole app in three sentences, it is the right size.

Which tool should you use?

It depends on how much code you want to see.

  • Lovable, Bolt and v0 build a working interface from a description in minutes. Best if you do not want to touch code.
  • Cursor, Windsurf and Claude Code work inside a real codebase on your computer. Best if you want to understand and own the code as it grows.
  • Supabase for the database and logins, and Vercel for hosting, are the default backend in a huge number of these builds, because both have a free tier.

You can start in a no code builder and move to a code editor later. Many people do exactly that.

How do you stop the app from breaking as it grows?

This is where most first projects die. Four habits fix most of it.

  1. One change at a time. Ask for one screen or one feature, test it, then ask for the next. Big requests produce big, tangled changes.
  2. Save working versions. Use the version history in your tool, or git if you are in a code editor. When something breaks, go back instead of asking the AI to fix its fix.
  3. Describe the bug precisely. Paste the error message and say what you clicked. "It doesn't work" gets a guess.
  4. Ask it to explain. Once a day, ask the AI to explain how the app is structured. You will catch confusion early.

When is it ready to share?

Sooner than you think. Put it online as soon as the main thing works, even if it looks rough. Real users find the problems that matter in an afternoon.

Then post it. On AfterPrompt, share what you built, the tools you used, the prompts that got you there and what did not work. People who have hit the same wall will tell you how they got past it. Browse lessons on coding to see what others learned building theirs.

Frequently asked questions

Do you need to know how to code to vibe code?

No, not for a first small app. Knowing the basics helps once the app grows, and building with AI is one of the fastest ways to learn them.

How long does it take to vibe code an app?

A small, focused app can be working in a day or a weekend. Larger apps take longer mostly because of testing and fixing, not writing.

What is the biggest vibe coding mistake?

Asking for too much at once. Build one screen or feature at a time and save a working version after each step.

Is vibe coding good enough for a real product?

For a first version, often yes. Many products start that way. As it grows, someone needs to understand the code, so review and testing matter more.

Keep reading

Join the conversation.

Indie hackers, solo founders and AI enthusiasts, all in one feed. Follow them, ask them anything, share what you find. Free, two minutes.

Make your profile