Speedy Deploy

Documentation

Speedy Deploy builds in-app flows on the web and delivers them to apps already on your users' phones, without an app-store release. These pages explain the six ideas the product is made of.

The shape of it

Read these in order the first time — each one leans on the one before it.

  1. A flow is what people see. Screens, copy, and the order they come in. You build it in the browser and it renders natively on the phone.
  2. A placement is where your app asks for one. Your app names a spot — onboarding, paywall — and the placement decides which flow comes back. Your app never names a flow.
  3. An audience decides who qualifies. A placement holds an ordered list of lanes; each lane pairs an audience with the flow that audience gets.
  4. A metric says what counts as success. Defined once for the whole project, so two tests measuring the same thing really are measuring the same thing.
  5. The SDK is how your app asks and reports. One key, one call to show a flow, and the events that make the numbers move.
  6. Health tells you when delivery failed. Installs that asked for a flow and got nothing back — a separate problem from a flow nobody finished.

Two kinds of test

Both are called tests and they are not the same thing. A screen test lives inside one flow and its arms swap a screen. A flow testruns on a placement's lane and its arms are whole flows — that is the one that earns a flow the In a test badge. Screen tests are covered under flows, flow tests under placements.

Where to start

Setting up a project for the first time: create a flow, which mints a placement for it. Add an SDK key for your staging build and wire configure() and present(). Publish to staging, confirm the flow appears, then publish to production. Audiences, tests and metrics are worth adding once something is live and you know what you want to change about it.

A word that gets mixed up

A flow is content; a placement is an address. The same flow cannot be served at two placements — publishing it has to have one answer. If you want the same screens in two places, copy the flow.

Your app, your responsibility

Flows are declarative content rendered by the SDK, not downloaded executable code. You remain responsible for your app's compliance with the app stores' policies on remotely delivered content, and for what your flows ask your users.