Conversation
| keywords: ['paywall builder', 'old paywall builder', 'move to new builder', 'paywall migration'] | ||
| --- | ||
|
|
||
| If your current paywall was made in the old Paywall Builder, you can convert it into a flow without rebuilding it. <Inline id="move-to-new-builder.svg" alt="Move to new builder" /> **Move to new builder** recreates the paywall as an editable flow in one click. Layout, text, products, and localizations carry over. Your original paywall stays live and unchanged, so you can build and test the flow before you switch to it. |
There was a problem hiding this comment.
Move to new builder
Не крит вообще, но вопрос ленивого человека: зачем добавлять иконку тогда, когда есть текст, которого хватает для идентификации кнопки/функциональности? Мб, будем иконки вставлять только тогда, когда нет текста?
|
|
||
| If your current paywall was made in the old Paywall Builder, you can convert it into a flow without rebuilding it. <Inline id="move-to-new-builder.svg" alt="Move to new builder" /> **Move to new builder** recreates the paywall as an editable flow in one click. Layout, text, products, and localizations carry over. Your original paywall stays live and unchanged, so you can build and test the flow before you switch to it. | ||
|
|
||
| ## What carries over |
There was a problem hiding this comment.
А мы как будто уже это пишем в последнем предложении интро. Можно его отдельным абзацем вынести, и тогда эта секция уже не так нужна будет
|
|
||
| The new flow is a separate copy. Your original paywall keeps running until you decide to switch. | ||
|
|
||
| ### Known limitations |
There was a problem hiding this comment.
Давай сделаем это последней секцией в статье. Это же то, что мелким шрифтом в конце договора пишут, и это больше для референса
| - **Hero images and videos**: A full-width image or video may not carry over exactly as in the original paywall. | ||
| - **Media overlays**: Flows don't support overlay images yet. | ||
| - **Image tint and mask**: Neither carries over. | ||
| - **Custom fonts**: Fonts don't carry over on their own. [Upload the fonts and manually style the text](using-custom-fonts-in-flow-builder) after the conversion. | ||
| - **Layer order**: A known z-index bug can stack some elements in the wrong order. | ||
| - **Relative sizing**: Flows can't size elements as a percentage of the parent. | ||
| - **Maximum width**: Flow elements don't have a maximum width setting. | ||
| - **Spacing and padding** may drift insignificantly. |
There was a problem hiding this comment.
Вообще такой большой список грустно звучит, не хочется всем его показывать... мб, что-то к релизу исправят?
Хочется и честными остаться, и людей не пугать — как будто можно попробовать более общими словами обрисовать
|
|
||
| To convert a paywall into a flow, open the paywall's overview page and click <Inline id="move-to-new-builder.svg" alt="Move to new builder" /> **Move to new builder**. | ||
|
|
||
| The <Inline id="move-to-new-builder.svg" alt="Move to new builder" /> **Move to new builder** button only appears for paywalls made with the old Paywall Builder. Paywalls built by hand need to be [recreated manually](paywall-builder-templates). |
There was a problem hiding this comment.
Paywalls built by hand need to be recreated manually.
Меня бы это смутило как пользователя, потому что мы этот сценарий вообще никак не упоминаем. Да и зачем им кастомные пэйволы мигрировать
| ## Why you should migrate | ||
|
|
||
| With separate onboardings and paywalls, you maintain two builders and two placements. You also hand users off from the onboarding to the paywall in your own code. | ||
| Adapty is sunsetting the standalone paywall and onboarding builders. Flows already offer native rendering, superior performance, and a richer feature set. New features will only ship to flows. | ||
|
|
||
| A flow replaces both with one experience — intro screens, a quiz, and the purchase screen — built in one editor and served from one placement. | ||
| Flows also replace two builders and two placements with a streamlined experience, so there's less to build and maintain. And moving is easy — you can convert your paywall builder creations in one click. | ||
|
|
||
| The table below compares what each option gives you: | ||
| Your existing onboardings and paywalls keep working, so nothing breaks before you migrate. Move at your own pace. |
There was a problem hiding this comment.
Это можно ворнингом в конце интро сделать вообще
И сократить в духе "С 1 октября пэйволы и онбординги превратятся в тыкву. Успей перейти на флоу — ты ничего не теряешь, и это довольно легко"
| Migration takes three steps and minimal code changes. If you used the old paywall builder, the design can be converted with a single click. | ||
|
|
||
| Your existing onboardings and paywalls keep working, and Adapty continues to support them. New features, however, now ship to flows rather than to the standalone onboarding and paywall builders. | ||
| 1. **[Convert or recreate your paywall](#convert-your-paywall-or-recreate-it-by-hand)**. If a paywall is made with the old Paywall Builder, you can convert it to a flow with a single click — no developer needed. Any other paywall or onboarding needs to be [manually recreated](paywall-builder-templates). |
There was a problem hiding this comment.
Any other paywall or onboarding needs to be manually recreated.
Звучит грустно! Мы в основном здесь про этот кейс и пишем, а другое лучше не упоминать пока. Пока что никто не спрашивал "как повторить мой кастомный пэйвол" или "как мигрировать мой онбординг"
| 2. **[Preview on device](#preview-on-device)**: Check the flow on a real device through the Adapty mobile app; no app build needed. | ||
| 3. **[Create a new placement for your flow](#create-a-new-placement-for-your-flow)**: Create a new flow placement with its own unique ID, and decide how it coexists with your existing placements. | ||
| 4. **[Update the SDK](#update-the-sdk)**: Upgrade to iOS, Android, React Native, or Capacitor SDK v4, fetch the flow from its placement, and verify a sandbox purchase. This is the main developer task. | ||
| If you built the paywall by hand, or you're migrating an onboarding, one-click conversion isn't available. [Create a flow](paywall-builder-templates) from one of the available templates — or completely from scratch. |
| Main article: [Convert a paywall into a flow](convert-paywall-to-flow) | ||
| ::: | ||
|
|
||
| :::warning |
There was a problem hiding this comment.
то же самое — лучше убрать
|
|
||
| Start from Scratch creates a flow with a single blank screen. Design the screen with elements from the [elements library](builder-elements). | ||
|
|
||
| ## Convert an existing paywall |
There was a problem hiding this comment.
тут можно сформулировать в духе Migrate a paywall from the legacy Paywall Builder, чтобы было яснее + так добавишь кивордов
No description provided.