Launch checklist for a vibe coded app

A working launch checklist for founders who built with AI. It covers the flows, the edges and the basics a user notices on day one. The security half has its own checklist.

Last reviewed 2026-09-30Written by Jacob Masse, TrazTech Inc.

Before launching an app built with AI, walk every core flow as a brand new user, then try to break each one with bad input, double clicks, the back button and a phone. Confirm every email arrives, every payment state is handled, and that you will know when something fails in production. Most launch-day bugs in AI-built apps are in the edges the demo never visited.

Core flows

0 of 0 done · Reset

• Sign up with a new email, confirm it, and complete onboarding
• Do the main thing your product exists for, start to finish
• Invite a teammate, if the product supports teams
• Upgrade, downgrade and cancel a plan
• Delete an account and confirm the data goes
• Log out and back in on a second device

Edge cases

0 of 0 done · Reset

• Empty, very long and emoji text in every field
• Zero, negative and very large numbers
• Names with accents and apostrophes, and French characters
• Double-click every submit button
• Back, refresh and a copied deep link on every step
• Two browser tabs editing the same thing
• Time zones and dates around midnight and daylight saving

Devices and browsers

0 of 0 done · Reset

• A real iPhone in Safari
• A real Android phone in Chrome
• A narrow window on desktop
• Keyboard-only navigation of the main flow

Email and payments

0 of 0 done · Reset

• Every transactional email arrives and is not in spam
• Emails come from your domain with SPF, DKIM and DMARC set
• A declined card leaves the account in a sensible state
• A refund removes access
• Receipts show the right tax, including HST or GST where it applies

Operations

0 of 0 done · Reset

• Errors are logged somewhere you will see them
• You can roll back to the last working version
• Backups exist and you have restored one
• A status or contact route exists for users when things break

Security basics

The launch checklist assumes the security basics are done. They have their own list: the pre-launch security checklist. The two together are what a professional QA test and security test verify.

Common questions