# The checklist I run before a vibe-coded app goes live

> A developer's pre-launch checklist for apps built with Lovable, Bolt, Replit or Cursor: data access, secrets, payments, hosting, backups and app stores.

By Tommy Pham · 2026-11-14 · https://tommydev.web.app/blog/vibe-coded-app-production-checklist

**Short answer:** before real users touch an AI-built app, check seven things: who can read whose data, which secrets reach the browser, whether payments are confirmed server-side, where it's hosted, whether you can restore a backup, whether you'll know when it breaks, and that a stranger can sign up and pay without help. Each section below links to a detailed guide.

I'm a full-stack developer, and I've shipped production apps to the web, the App Store and Google Play ([my work](/#work)). This is the list I go through when someone asks me to look at their app before launch.

## 1. Can users read each other's data?

The most common serious bug in AI-built apps. The login works, but the database lets any logged-in user, or anyone at all, read every row.

- **Supabase:** every `public` table needs Row Level Security on, with policies that scope rows to the user. → [Supabase RLS guide](/blog/supabase-rls-vibe-coding)
- **Firebase:** Security Rules must check ownership, not just `request.auth != null`.
- **Test it:** make two accounts and try to read A's data as B. Then try while logged out.

## 2. Which secrets reach the browser?

Anything in a `NEXT_PUBLIC_`, `VITE_` or `EXPO_PUBLIC_` variable is public. AI API keys, Stripe secret keys and Supabase service role keys must stay on a server.

- Build the app and search the output for `sk_`, `sk-`, `service_role` and connection strings.
- Rotate anything that ever shipped. → [Which API keys are safe in your frontend](/blog/api-keys-frontend-security)

## 3. Are payments confirmed by the server?

- Access is granted from a **verified webhook**, never from the "thank you" page.
- Cancellations, failed renewals and refunds remove access.
- In-app digital purchases on iOS and Android follow the stores' billing rules, which now vary by region.
- → [Stripe vs Polar](/blog/stripe-vs-polar)

## 4. Is the auth flow complete?

- Email verification and password reset work end to end, with emails that don't land in spam.
- OAuth redirect URLs point at the production domain, not `localhost` or the builder's preview URL.
- Sessions expire, and logging out actually logs out.
- → [Firebase Auth vs Supabase Auth](/blog/firebase-auth-vs-supabase-auth)

## 5. Is it hosted somewhere that fits?

- The free plan allows commercial use. Vercel's Hobby plan, for example, is for personal, non-commercial use only.
- Long tasks run as background jobs, not inside requests that time out. → [Background jobs guide](/blog/background-jobs-cron-trigger-dev-vs-cloudflare)
- You're on your own domain with HTTPS. → [Where to host a vibe-coded app](/blog/where-to-host-vibe-coded-app)

## 6. Can you recover from a bad day?

- **Backups exist, and you've restored one** at least once. Free database tiers often have limited or no point-in-time recovery.
- **There's a staging copy** (a preview deploy plus a separate database) so changes don't go straight to users.
- **The code is in GitHub**, in an account you own. → [Moving a Lovable or Bolt app off the builder](/blog/export-lovable-app-deploy)

## 7. Will you know when it breaks?

- Error tracking (Sentry, PostHog or your host's logs) is on, and someone gets alerted.
- An uptime check pings the homepage and one logged-in endpoint.
- Analytics show signups and payments, so a silent failure shows up as a drop.

## 8. Basics people skip

- [ ] Privacy policy and terms, especially if you collect personal data or take payments
- [ ] Rate limits on login, signup and anything that calls a paid AI API
- [ ] File uploads restricted by size and type, stored in non-public buckets
- [ ] Sitemap, page titles and share images. → [Launching an AI-built app](/blog/launch-vibe-coded-app)
- [ ] Removed debug pages, test accounts and seed data
- [ ] A stranger has signed up, used the core feature and paid, on a phone, without you helping

## Going to the app stores?

That's its own checklist: signing, store listings, review guidelines and testing requirements.

- → [Publishing a web app on Google Play as a TWA](/blog/pwa-to-google-play-twa)
- → [Shipping an Expo app to the App Store](/blog/expo-app-store-submission)

## FAQ

### How long does this checklist take?

For a small app, the checks themselves take an afternoon. Fixing what they find depends on the app: wrong RLS policies can be a quick fix, while untangling payments can take days.

### Can the AI builder fix these issues itself?

Often, if you ask precisely ("enable RLS on every table and add policies so users only read their own rows"). Verify the result with the tests above, because builders sometimes write policies that look right and aren't.

### What's the single most important item?

Number 1. Leaked user data is the failure you can't undo.

---

If you'd like me to run this checklist on your app and write up what I find, I do that as a freelance job. See [my work](/#work), or read [when to hire a developer](/blog/hire-developer-vibe-coded-app) first.