Welcome to the CtrlApp Handbook
A practical, step-by-step guide to remote-controlling your app with CtrlApp — from your first kill-switch to a safe production rollout.
CtrlApp is the remote control layer for your app. You keep the code you already have, add a small SDK or a single HTTPS call, and gain the ability to flip a switch — kill a broken feature, turn a flag on, change copy, force an update — without shipping a new release.
Read this handbook in order
- How CtrlApp works — the mental model.
- First working integration — a runnable REST-first tutorial.
- Core concepts — apps, environments, devices, controls, flags.
- Choose an integration — REST vs SDKs, and what is available today.
- Production checklist — before you enable a kill-switch on real users.
Conventions
- Placeholders look like
<APP_ID>,<PUBLISHABLE_KEY>,<DEVICE_ID>. - Every code block is copyable. Language and file name are labelled.
- Dashboard paths use the exact labels from the current UI, for example Dashboard → Apps → your app → API keys.
- Availability badges say Available, Preview, or Dashboard-only.
Never expose server-side secrets in client code
Publishable / SDK keys are safe to ship in mobile or browser binaries. Signing secrets and admin credentials are not. When in doubt, read API keys & secrets.