Fictura
App launch

Launch checklist

Everything worth verifying in the hour before you submit — each item checkable from the dashboard, none requiring faith.

Keys and config.

Growth.init carries the production apiBase and this app's gk_ key. Launch once and confirm app_open lands in the event dictionary.

Billing spine connected.

The RevenueCat webhook is pasted and a sandbox purchase shows up as trial_started / subscription_started. Sandbox events are isolated — they'll never pollute production entitlements.

Paywall live for every placement the app requests.

Dashboard → Paywalls warns about placements with nothing configured. An unconfigured placement renders your fallback — make sure that's a paywall, not a blank.

Web checkout, if you're using it.

Stripe connected, price picked, return deep link set, toggle on — then the test flow: system browser opens, test card pays, app is premium in ~15 seconds.

Push permission line in place.

registerForPush() after your permission moment — the SDK never prompts on its own, so if you never call it, you'll launch with zero tokens.

Error tracking smoke-tested.

Backend: python -m fictura (or the Node equivalent) puts events on the Issues page in seconds. App: Growth.captureError(new Error("launch check")) in a dev menu.

Uptime monitor pointed at your API.

One URL on the Issues page — 60-second checks and a down alert beat finding out from reviews.

Alerts reach a human.

Slack or email connected and the test message seen. Launch week is exactly when first-seen errors spike.

On this page