Ship your first build
From an empty dashboard to an app fetching live config: the shortest honest path through the whole system.
Create the app.
Dashboard → New app: name, category, and your store commission and tax. You get the two credentials everything else uses — the SDK app key and the RevenueCat webhook URL. Create an app.
Wire the SDK.
One package, one Growth.init, one provider — the SDK Quickstart is ten minutes. Launch the app once and watch first_open and app_open arrive in the event dictionary.
Connect billing.
Paste the webhook URL into RevenueCat. Trials, purchases and cancellations start feeding entitlements, churn states, and revenue.
Put a paywall live.
Dashboard → Paywalls: generate one with AI or start from a template, preview it on the phone frame, set it live. Devices show it on their next config refresh.
Work through the Setup checklist.
Dashboard → Setup keeps an honest checklist — every tick is computed from real data (events flowing, webhook seen, paywall live), not from you clicking "done".
Building from zero instead?
The App Builder (Dashboard → Build) is an agent chat that scaffolds a working Expo app — sessions, file tree, live preview — with the SDK, your keys, and a growth.defaults.json already wired. Publishing an update is OTA: installed apps pick it up on next launch. The Build tab lists projects across all your apps (each project belongs to one app), and a connected Supabase org gives builds a backend you own.