You built an app with AI, it works on your laptop, and you want to send someone the link. Give it ten more minutes first. These are the three things I'd check, in this order, because they are what a stranger meets first: how it looks, whether the form works, and whether their data is safe.

The box above has one prompt that runs all three inside your AI coding tool. Or do it by hand, below.

1. Lose the purple gradient

A purple-to-blue hero with "Welcome to MyApp" and a "Get Started" button is what AI tools build when nobody tells them otherwise. So a lot of apps open the same way, and yours looks like the rest before anyone has tried it.

By hand:

  1. Open your first screen and read the headline. Does it say what the app does, or could it sit on any app?
  2. Replace the gradient with one plain background colour.
  3. Rewrite the headline as the thing a person gets: "Water your plants on time", not "Welcome to PlantApp".
  4. Rename the button after what it does: "Add my first plant", not "Get Started".

The longer version, with the code: how to remove the purple gradient hero.

2. Fill in your own form, on your phone, badly

Forms are where these apps quietly break. The AI built the version that works on its first try: a wide screen, a fast connection, a correct email. Real people bring small phones, dark mode and typos.

By hand:

  1. Open the app on your phone, not in a narrow browser window.
  2. Is the whole submit button on the screen?
  3. Type a wrong email and leave a field empty, then submit. Do you get a clear message next to the field, with what you typed still there?
  4. Switch your phone to dark mode. Can you read what you type?
  5. Tap submit twice, fast. Did it send twice?

All eight form checks: how to fix forms in vibe-coded apps.

3. Try to change someone else's data

If your app has accounts or a database, this is the one that matters most. In one of my own apps, someone gave a student 90 million points, because the database checked who could write and never what they wrote.

By hand:

  1. Make a second account with a different email. That's your stranger.
  2. Signed in as the stranger, can you see anything the first account made?
  3. Can you edit or delete it? Try the app's own buttons first. Then ask your AI tool: "As a signed-in user who doesn't own this row, what can I read or change?"
  4. Open the app signed out, in a private window. What can you see?
  5. If you use Supabase, check that row level security is on for every table (Table Editor shows a warning when it's off).

If you can change it, so can anyone. What we did about it: row level security is not enough.

No accounts and no database? Skip this one. Two out of two is fine.

Then share it

Three ticks and the link is ready to send. It won't be perfect, and it doesn't have to be. It only has to not fall over in front of the first person who opens it.

When you want to go further, the free Finish It pack has the prompts from all these guides in order.

References