Notes · Vibe-coded apps

Your vibe-coded app works. Here is what breaks when real users arrive.

An app built with AI tools can look finished and still fall over at launch. These are the six places it usually happens, and how to check your own.

← All notes
Published
20 November 2026
Reading time
3 minutes
Topic
Vibe-coded apps

You described what you wanted, an AI tool wrote it, and now there is a working app on your screen. That part is real, and it used to take months.

What the tool built is a demonstration. It proves the idea. It has been used by one person, on one device, who knows which buttons to press. Launching means strangers, many of them at once, some of them trying to break it.

The gap between those two is where we spend our time. It nearly always comes down to the same six things.

The six places it breaks

  1. 01Secrets in the openAPI keys and passwords sit in the code or in the browser, where anyone who looks can copy them.
  2. 02Logins that trust the userChange a number in the address and you are looking at someone else's account.
  3. 03No way backThe database has no backup, or it has one nobody has tried to restore.
  4. 04Nothing checks it worksThere are no automated tests, so every change is a gamble on everything else.
  5. 05Copy and paste everywhereThe same logic lives in five files. Fix a bug in one and it survives in four.
  6. 06Releases by handGetting a change live is a set of steps only one person remembers.

None of these show up in a demo. All of them show up in the first month of real use.

Why AI tools leave these gaps

It is not that the tools write bad code. Line by line, it is often good.

The problem is what they are asked for. "Make the sign-up page work" gets a sign-up page that works. Nobody asked what happens when two people sign up with the same email, or when the payment provider is down, so nothing handles it.

AI tools also work one request at a time. Each answer is reasonable on its own. Forty reasonable answers, never read together, make a codebase where the same job is done three different ways.

The app is not wrong. It is unfinished in the places you cannot see.

Check your own in ten minutes

You do not need to be a developer for the first pass.

  1. Search the code for the word "key". If you find a long string of letters and numbers next to it, that secret is exposed.
  2. Sign in as one user, copy an address with a number in it, and open it as another user. If the page loads, your data is not private.
  3. Ask where the backups are. Then ask when one was last restored.
  4. Ask how many tests there are. If the answer is none, nothing is protecting what already works.
  5. Ask what happens if a release goes wrong. "We fix it quickly" is not a way back.

If any of those gave you an uncomfortable answer, that is normal for an app at this stage. It is also fixable.

What fixing it looks like

The order matters. Security comes first, because it is the one that hurts other people. Tests come second, because they make every later change safe. Tidying the structure comes third, once the tests can prove nothing broke.

  1. 01Read all of itEvery file, plus the app running. Risks are written down and ranked.
  2. 02Close the holesSecrets moved out of the code. Logins and permissions checked on every route.
  3. 03Add the testsThe paths that earn money or hold data are covered first.
  4. 04Tidy the structureDuplicates merged, dead code removed, the half-built parts finished.
  5. 05Make releases boringOne repeatable step, an alert if it fails, and a way back.

Usually the app survives. A rebuild is only worth it when the fixes would cost more than starting again, and you should be shown both prices before anyone starts.

Keep building with AI afterwards

Hardening an app does not mean giving up the tools that built it. It makes them work better.

An AI tool changing an app with no tests is guessing. The same tool changing an app with tests gets told, within seconds, exactly what it broke. A clear structure means it changes one place instead of five.

So the aim is not to replace the way you work. It is to put a floor under it.

If you would like a second pair of eyes on your own app, that is what this service is for.

Next note · Vibe-coded appsWhat production-ready actually means: the twelve things we check →
Book a call