Free · ~20 minutes

Pre-launch checklist for vibe-coded apps

A short list for founders about to share a real link — built with Lovable, Bolt, Base44, Replit, v0, Cursor, or similar.

Open your app in a normal browser tab (not the builder preview). Check what you can. Fix what you can. Get help for the rest.

Want the longer version? Full checklist on GitHub (optional deep checks).

How to use it

1. Work through each section — about 20 minutes total.
2. Mark each line: done, problem, or not sure.
3. Problems become your fix list. “Not sure” is a good reason to get a second pair of eyes.

This is what visitors notice — not a code review or security audit. For deep security, tools like VAS complement this well.

1. First look

~5 minutes · homepage and footer

• The live link loads without feeling broken or endlessly spinning
• The browser tab shows your app name (not “My App” or generic builder text)
• A stranger can tell what your app does within a few seconds of reading the homepage
• No placeholder text left behind (lorem ipsum, “Your Company Name,” “[insert tagline],” obvious TODO notes)
• No default “welcome to your new app” copy from the builder — it sounds like your product
• Your product name appears in the header, not the platform’s logo as the star
• Nothing obviously “for developers only” on the public site (test data buttons, skip-login, seed sample data)
• The main button on the homepage does what it promises when you click it

2. Trust & contact

~3 minutes

• Privacy policy page works (often at /privacy)
• Terms page works (often at /terms)
• Visitors can find how to reach you (support email in footer or a contact page)
• That email is real and one you check — not support@example.com
• Footer links to privacy and terms work (no “page not found”)

3. Does the main flow work?

~10 minutes · the one thing users come to do

• Buttons and menu links you tried actually do something (no dead ends)
• If people sign up: confirmation email arrives (check spam)
• If people sign up: you can log in afterward with that account
• If people sign up: you can log out
• The core workflow finishes — book, pay, submit, save, whatever your app is for
• After submitting a form, you see a clear “it worked” or “something went wrong” message
• If you charge money: a test payment completes and shows a sensible thank-you page
• A brand-new user isn’t staring at a totally blank screen with no hint what to do next

4. On a phone

~5 minutes · open the site on your phone or narrow the browser window

• No sideways scrolling — everything fits the screen width
• Text is readable without pinching to zoom
• Buttons are easy to tap (not tiny)
• The main workflow is usable on phone, not only on desktop

5. Sharing your link

~2 minutes

• Paste your URL into Slack, iMessage, or LinkedIn — the preview shows the right title and description (not generic builder fluff)

6. If people can sign in (optional)

Skip if your app has no accounts · otherwise create two throwaway test accounts

• Signed in as person A, you cannot see person B’s private stuff (messages, files, bookings, etc.)
• When signed out, opening “dashboard” or “settings” asks you to log in — it doesn’t show someone else’s data

Need a thorough two-account review? That’s included in Full Package ($29).

7. Gut check

~2 minutes

• You’d be comfortable sending this link to a friend today
• You wouldn’t be embarrassed if someone screenshotted the homepage

What to do next

• Fix before you share widely: broken signup, missing privacy/terms, placeholder text, dev-only buttons still visible, one user seeing another’s data.
• Fix soon after launch: mobile layout quirks, weak link previews, empty screens without guidance.
• More than ~5 serious problems? Pause the launch push until the worst ones are handled.

Free to copy and share. Maintained by LaunchLook.