Flows

The screens that decide whether a user subscribes — the welcome sequence, the survey that personalizes the pitch, the permission prompt, the paywall itself — are almost never the screens you can change. They are hard-coded, stitched together across releases, and locked behind the next app store review. So the moment you want to ask one more question, swap the order of two steps, or test whether the paywall should come on screen three instead of screen six, you are filing a ticket and waiting weeks for an answer you could have had today.

Flows is how growth teams take that whole journey back. It lets you build a connected, multi-step experience — onboarding, surveys, permission prompts, and paywalls — on a single visual canvas, then test and reorder any part of it without shipping a build.

String every step into one experience

A flow strings multiple pages together into one seamless journey, built in the same editor you already use for paywalls. On the canvas you see the entire experience at once — every page, and every connection between them — instead of imagining how a sequence of hard-coded screens will actually feel.

Explore the canvas

Each page is built from the full editor toolkit, so your onboarding looks and behaves like the rest of your app, not a generic form. You can drop in:

• Multiple-choice and single-select questions to qualify users and segment them early.

• Text input fields to capture names, goals, or anything you want to personalize on later screens.

• Progress indicators so a long sequence feels short and completion rates stay high.

• Native permission prompts — notifications, location, camera, contacts, tracking, and more — that fire at the right step and advance the user automatically based on whether they grant or deny.

• Your real paywalls, placed exactly where the journey has earned the ask.

Branch on what the user tells you

A funnel that treats everyone the same leaves conversion on the table. Flows uses navigation and routes to send users down different paths based on the answers they just gave — a beginner sees a different sequence than a power user, a churned customer sees a different save offer than a fresh install. You wire the branching logic visually on the canvas, no engineering involved.

Rewire and rewrite without a release

This is the part that changes how a growth team works. Superwall paywalls and flows render from a web-standards runtime that is preloaded on device, so editing a flow in the dashboard pushes the change straight to live users. The order users actually experience is defined by routes, not by where pages sit on the canvas — so you can rewrite copy, add a branch, or move the paywall earlier in the sequence by rewiring the flow, and it takes effect without an app store submission or an SDK upgrade.

See navigation and routes

The same flow can run across web and mobile, which means a web acquisition funnel and an in-app onboarding can share structure and stay in sync instead of being maintained as two separate code paths.

Test the structure, not just the screen

Because flows are configured remotely, every part of the journey is testable the same way a paywall is. Run experiments on onboarding length, question wording, where the paywall appears, and whether a permission prompt belongs before or after the pitch — then ship the winner to everyone by adjusting traffic, with no new build in the loop. The flow analytics show you each step rather than a single open-or-converted event: you can see exactly where users drop off and compare how different flow variants move people through the funnel.

What you can build

• Onboarding sequences that qualify users, personalize the pitch, and hand off to the right paywall.

• Cancellation and save flows that branch on the reason a user gives and route them to a matching offer.

• Permission moments timed to the step where users are most likely to say yes.

• Web qualification funnels that warm up traffic before the app or checkout.

• Segmented welcome experiences tailored to where a user came from and what they told you.

Get started

Build your first flow on the canvas — see getting started with flows for the walkthrough, or read the onboarding flows guide for a full example. You can start for free and have a testable journey live without waiting on a release.

Get started with flows