Launch checklist

A short list to run through before you put your app in front of real users.

Before your first publish, a few minutes of checking saves a lot of after-the-fact fixes. Here's what's worth confirming.

If your app has accounts, sign up as a brand-new user in the preview — not as the test user, whose session may already be valid. Then sign out and confirm a protected page actually redirects rather than rendering.

Check Settings → Cloud → Users afterwards and clear out the test accounts you don't want in your live app.

Keys are the live ones

If you built against a provider's sandbox, swap the value under Settings → Cloud → Secrets to the live key before real transactions run — and publish again afterwards, since the change reaches your users at the next publish. See Secrets.

This cuts both ways: a live key set too early means real charges during testing.

Real content, not placeholders

Swap out any lorem-ipsum, sample logos or test copy for the real thing. Check the empty states too — what someone sees before they've added any data is often the first screen a new user meets.

It works on a phone

Most visitors arrive on mobile. Switch the preview to a small screen and walk the main flow to make sure nothing is cut off or cramped.

Emails come from you

If your app sends email — sign-up confirmations, receipts — set up custom emails under Settings → Cloud → Email so they arrive from your own domain rather than a generic address. Send yourself a test and check it doesn't land in spam.

Google and Microsoft sign-in only complete on a published URL, so it can't be verified in the preview. Publish first, then test the button on the live site. See Social login.

Set your custom domain if you have one, and check the title and preview image that show when the link is shared — see SEO.

Scheduled jobs won't surprise you

If you set up any scheduled jobs, especially ones that delete or email people, watch the first run in Settings → Cloud → Jobs before leaving them unattended.

Then publish

Happy with all of the above? Publish — and remember you can keep shipping updates and roll back if anything slips through.

Next steps

Deploying your app — the publish itself
Analytics — watching the first arrivals
Logs and monitoring — catching what goes wrong