Paywall Builder and Onboarding Builder deprecation

On October 1, 2026, Adapty deprecates the legacy Paywall Builder and Onboarding Builder in favor of Flow Builder. Everything you’ve published keeps working: your users keep seeing your paywalls and onboardings, and your data stays in place. You can still edit your existing paywalls and onboardings. The deprecation turns off creating new ones and ends support for the legacy builders.

What keeps working

The deprecation doesn’t change anything for your users, and your existing paywalls and onboardings stay editable:

• Published paywalls and onboardings: The Adapty SDK keeps rendering them in your apps, on the placements they’re assigned to today.
• Editing: You can still edit your existing paywalls and onboardings in the legacy builders.
• Your data: Paywalls, onboardings, and their metrics stay in your dashboard. Nothing is deleted.

What stops on October 1, 2026

From that date, in the legacy builders:

• No new paywalls or onboardings: You can’t create them in the legacy builders. Build new ones in Flow Builder.
• No support: Adapty no longer ships fixes for the legacy builders.

Custom paywalls stay available

The deprecation covers the two visual builders, not the paywall itself. If you build your paywall UI in your own app code and use Adapty as the purchase infrastructure, the deprecation doesn’t apply to you.

You keep creating paywalls to define which products you sell, and assigning them to placements. You can still add an optional remote config to a paywall to change copy and media without an app release. Your app fetches the paywall’s products and calls makePurchase — see Render your own paywall UI and delegate purchases to Adapty iOS, Android, React Native, Flutter, Unity, Kotlin Multiplatform, and Capacitor .

Move to Flow Builder

A flow combines onboarding screens and a paywall into one experience, built in one editor and served from one placement — a new flow placement, because a flow is a different content type from the paywall or onboarding it replaces. For the whole path — build the flow, preview it on a device, create a flow placement, and update your app to Adapty SDK v4 — follow Migrate to flows.

Convert your paywall in one click

You don’t have to rebuild a legacy paywall by hand. The Move to new builder action recreates it as a draft flow, carrying over the layout, the copy in every locale, and the products with prices as variables. Your original paywall stays live and unchanged while you edit and test the flow — see Convert a paywall into a flow.

For a flow that goes beyond the original paywall — a quiz, branching, several locales — the flow-generator agent skill builds and edits flows from your terminal through your own AI coding tool.

Plan for two steps a legacy paywall didn’t ask of you:

• An app release: Flows render on Adapty SDK v4 and later, so users see your flow only after they update to an app version built with it. Start the SDK upgrade now, so a v4 release is already live when your first flow is ready.
• A new placement: A converted flow doesn’t inherit the paywall’s placement, and it can’t reuse that placement’s ID — placement IDs are unique across your whole app. Create a flow placement with a new ID, and keep the paywall’s placement live for the app versions that still call it.

If a paywall drives most of your revenue and you don’t want to switch all of its traffic at once, roll the flow out gradually: serve it to a small share of users alongside the existing paywall, compare conversion, and raise the share as the results hold up.