Lovable App Launch Checklist

1. Make a real purchase on the live checkout. Pay with a real card, then refund yourself — and confirm the receipt email and any post-purchase state actually update.
2. If you use Supabase, turn on Row Level Security everywhere. With RLS off, anyone holding your public anon key can read the table. Verify policies on every table with user data, then test with a second account.
3. Confirm secret keys never reach the browser. Search the deployed bundle for key-shaped strings; anything secret belongs in server-side functions or environment secrets.
4. Re-click old flows after late prompt changes. Regenerating one screen can quietly change shared components — re-test signup and checkout after any last-minute edits.
5. Run the full auth loop, including the emails. Sign up, log in, log out, password reset — and confirm the reset email arrives at an address outside your own domain.
6. Point your custom domain and force HTTPS. Check both the apex and www, and that plain http redirects cleanly.
7. Open the app as a brand-new user. Every list, dashboard, and table needs a designed empty state, not a blank panel.
8. Submit every form wrong on purpose. Empty, bad email, oversized input — each needs a visible, recoverable error.
9. Visit a nonsense URL and hard-refresh deep routes. Single-page apps commonly blank or 404 on inner-page refresh when rewrites are not configured — test each route by URL.
10. Test at 375px wide. No horizontal scroll, readable type, thumb-sized tap targets.
11. Set your title, description, OG image, and favicon. Then paste the link into a chat and check the preview card a stranger sees.
12. Rewrite generated policy pages so they are true. Placeholder refund or privacy text you do not honor is worse than none — a policy is a promise.
13. Scan the landing copy for claim risk. Guarantees and invented numbers slip into generated marketing copy easily; cut anything you cannot prove.
14. Practice a restore before launch day. Confirm you can roll back to a previous published version, and do it once so the revert is not theory.
15. Take an export and a database backup now. Download a copy of your project and a dump of the data — before launch, not after the first incident.
16. Publish a monitored contact address and write the launch-day plan. Who checks errors and payments, how often, and what would make you pause.

Checkboxes are for this visit only — nothing is stored, tracked, or sent anywhere.

7-day money-back guarantee

Everstead Labs offers a 7-day money-back guarantee on founding beta software purchases and paid launch-readiness audits. If it is not useful, contact us within 7 days of purchase and we'll refund you. The product provides launch-readiness signals and practical fix guidance; it does not guarantee revenue, legal compliance, security, app-store approval, or launch success.