TL;DR
Flow Builder is the next version of the Paywall Builder, now in iOS beta. Every paywall you’ve shipped keeps running; the new part is that you can wrap onboarding, surveys, and post-purchase screens around it and test the whole journey as one flow.
Flow Builder is live in beta, a native, no-code builder for your whole subscription flow, onboarding through paywall, in one place.
You already had both builders, one for onboarding and one for paywalls. They lived in separate tools, each with its own A/B test and its own numbers. So you could tune a paywall for weeks and never learn whether the real drop-off was a screen three steps earlier.
Flow Builder puts them in a single flow. The paywalls you’ve shipped and the onboarding you’ve built now live in one connected journey you design and test as a whole. If you’re already on Adapty, let me walk you through what moves and what stays put.
Does your current paywall still work?
Yes. Everything you’ve shipped keeps serving the same way it did yesterday, and nothing migrates on its own. The Paywall Builder stays fully functional. From here, though, new features and updates go into Flow Builder, so your live paywalls are safe, and your next build belongs in a flow.
Moving over costs you nothing. Flow Builder does everything the Paywall Builder did, including plain single-screen paywalls, and every element, theme, product tag, remote config, and localization you set up carries straight into a flow. When you want onboarding in front of a paywall, you build the flow and point your placement at it.
On Enterprise and want your existing paywalls rebuilt as flows? Adapty’s team will do it with you.
What can you build in a flow?
A flow is a single object that holds the journey from the first onboarding screen through post-purchase. You test and measure it as one funnel under one targeting rule, so you can see how the opening screen affects the conversion at the end.
The Paywall Builder gave you a single paywall screen. Flow Builder gives you everything around it, so you can build the paywall you sketched but gave up on with the old one. The pieces you work with:
- Build any screen you want. Start from a blank canvas instead of a fixed template, and lay it out yourself with text, images, video, and buttons.
- Ask questions and keep the answers. Multiple choice, text, email, or a number, and the flow stores each answer to use on later screens.
- Branch by what people pick. Send a beginner and a power user down different screens, so each one sees the version that fits.
- Add the finishing touches. Loading screens, progress bars, permission prompts, and elements that show only when they should.
With these, you can build almost anything: a single-screen paywall, a multi-step onboarding quiz, a free-trial signup with a personalized welcome, or a localized flow for a new market. For the full rundown of what’s possible, see what Adapty Flow Builder is.
How do you test the whole journey?
Flow-level A/B testing runs complete flows against each other. You measure a new onboarding sequence and a new paywall design together and see their combined effect on trial starts and paid conversion, instead of guessing which half moved the number.
Per-screen analytics show where users drop inside the flow. Revenue ties back to the exact paywall screen, flow variation, and placement that earned it, so you can follow the money from the first onboarding screen to paid conversion.
Can you target a flow by keyword?
Adapty owns the attribution layer (Apple Ads, Meta, TikTok) and the builder. So your flow can change based on how the user arrived, down to the keyword or the ad creative they tapped.
Someone who found you through the Apple Ads keyword “ai animation generator” already knows what they came for, so you lead with the paywall that matches it, animated AI characters, and a 3-day trial, and save the onboarding for after. Someone who tapped a broad video ad needs the value shown first, so they get the full onboarding before any ask. Organic users see the complete pitch.
You set this once as a targeting rule on the placement, and because the whole flow runs on one targeting engine, you never duplicate rules between onboarding and paywall.
How do flows render and update?
Your flows render as real native UI through the Adapty SDK. No WebView, so users never wait on an HTML page to load, and stores never flag the screen as a remote paywall. Adapty serves the configs over a CDN with 300+ points of presence, and offline fallbacks keep the flow on screen when a device loses its connection.
You edit a draft while the live version keeps running, then publish in one click, and the change reaches every user without an app release.
Is Flow Builder for you?
Probably yes, if any of these is on your list:
Personalize the flow. Ask a question on the first screen, then branch on the answer so each user sees the screens and the offer that fit them. One flow can sell to a few different audiences at once.
Win back churned users. Send cancelled subscribers into a win-back flow with a countdown timer on a discounted annual offer, shown only at a churned-user placement. The whole re-engagement sequence lives in one flow.
Upsell after the purchase. Add a post-purchase screen to the same flow, so the moment someone subscribes, you can offer an annual upgrade or an add-on, all in the sequence you already built.
Run a different flow per campaign. Target by Apple Ads keyword or ad creative, so paid traffic and organic traffic don’t open to the same screens. You set it once on the placement.
Should you migrate? Eventually, yes. New features ship to flows from here, so they’re the foundation worth building on. Nothing forces your hand, though. Your current paywalls and onboardings keep working, so move over when it fits your release schedule.
What’s in the beta today?
Flow Builder runs on iOS SDK v4 and above, and it’s ready to ship to real users now. Everything from the Paywall Builder is already in, so moving a paywall over loses nothing. On top of that, you get the parts a single paywall couldn’t do:
- Onboarding, surveys, and post-purchase screens in one flow
- Branching, variables, and scripts for personalization
- Flow-level A/B testing with per-screen analytics
- Native rendering over the CDN, with offline fallbacks
Beta means iOS only for now, with Android and the other SDKs in progress, and a few roadmap items below still landing. None of it touches your live paywalls, so build a flow against a test placement and try the whole thing without changing what’s running today.
What’s coming next?
For non-iOS teams, the item that matters most is platform coverage. Android and the rest of the SDKs (React Native, Flutter, Unity, Kotlin Multiplatform, Capacitor, Expo) are in progress, so Flow Builder will reach your whole stack before long.
The rest is about speed and polish. Some of it is already rolling out, so check the dashboard for what’s live:
- AI flow generation drafts a full flow from a plain-language prompt, the way you’d brief an AI coding agent.
- Responsive layouts fit one flow to small phones, large phones, and iPads with no separate builds.
- A template library so you start from a working flow instead of a blank canvas.
- Charts and screen animations for a more engaging onboarding.
- Figma import and “copy from my app” to rebuild the screens you already have.
Get started
Your first flow is an afternoon of work, and it ships without an app release.
- Update to the Adapty iOS SDK, v4 or later. That’s the one prerequisite.
- Open Flow Builder and build a screen or two. Start from a blank canvas (templates are coming) and drop in the paywall you already run.
- Add a survey question up front. Store the answer, then branch so each user lands on the screen that fits.
- Publish and point a placement in the flow. The change reaches users with no release.
- Watch the per-screen numbers and fix the screen that’s losing people.
The bottom line
If you’re on Adapty today, nothing you’ve shipped breaks, and you get a much bigger canvas the day you want it. Your paywalls stay exactly as they are.
Flows are where Adapty goes from here, so they’re where your next build belongs. The first one takes an afternoon, and the upside compounds every time you test.
