General overview

Purchasely Screen Composer provides an intuitive and flexible way to design custom screens for your app.

The module integrates a comprehensive library of pre-built components, that users can simply drag and drop into their screen structure and organize in different layouts to best fit their needs.

Screens can be created either from a white slate or from a pre-configured template that can be customized as desired, and on which components can be added / removed or reordered.

Once components are placed, they can be easily reordered and individually configured to match the desired design and branding. The layout can be adjusted at any time, providing full flexibility to adapt your design as your needs evolve. This ensures a seamless and dynamic experience in creating personalized app screens.

🚧
Retro-compatibility considerations and fallback Screen for old versions of the SDK
The Screen composer requires the version 5.0.0 of the Purchasely SDK and above.
This can be a problem as long as old versions of the app, integrating previous versions of the SDK (< 5.0.0) are in the air.
Be reassured, when creating a new Screen with the Screen composer, you can select a "legacy Screen" (built with the legacy Paywall Builder) and associate it with the new Screen.
Click on the dropdown containing the Screen name is the top bar, then select the fallback presentation / Screen to associate with this new Screen
If an old version of the SDK (< 5.0.0) tries to fetch the new Screen (built from the Screen composer) from a Placement, the fallback screen, compatible with the old version of the SDK, will be retrieved instead.

📘
Is this possible to migrate legacy Screen in the new Screen composer?
Unfortunately it is not possible to edit your old Screens and Paywalls built with the legacy Screen Builder in the new Screen Composer. You will have to replicate them.

General process for creating a Screen

The Screen Composer can be accessed by clicking on the button + Composer in the Screens section of your Purchasely Console

1. Paywalls only: define the Plans

If the Screen configured is a Paywall, start by defining which Plans will be available on the Screen

One of the Plans must be defined as the default Plan.

For components which are not specifically mapped with a Plan (like a carousel, or a bulleted list), if Tags are used within the associated Text elements, the SDK will compute the Introductory Offer eligibility based on the default Plan.:

It will display the Offer text if the user is eligible to the Introductory Offer of the default Plan, and the Regular Offer otherwise.

2. Choose the layout

Select the desired layout among the ones available

See Layouts for more details

3. Select the components

Add the desired components by clicking on the button "Add components" and drag & dropping the component in the Screen structure and reorder them the way you want

4. Configure each component

Configure each component individually and integrate your copy, contents and branding (including custom fonts)

5. Configure your Screen in dark mode (optional)

Each color (font, border, background etc...), image, video or animation can be set for dark mode

6. Localize your Screen (if necessary)

Localize every text of your Screen

7. Configure the Close button look and feel and behavior

Close button configuration details are provided here

Then hit Publish and you're all set!

Layouts

Layouts define the way the Purchasely SDK will organise and display the components on the device screen.

3 layouts are available for now:

Fill height: all the components of the Screen must fit in the device screen. If necessary, the Purchasely will expand one component to fill the whole device screen or shrink it. With this layout, the Screen is not scrollable even if it exceeds the height of the device screen.
See Layout fill height - expand to fill a component for more details
Scroll: this layout will stack the components from the top of of the device screen. No component will be expanded if they don't fill the height of the device screen and a scroll bar will be displayed if they exceed the height of the screen.
Sticky bottom: this layout features 2 different "surfaces" to which components can be associated. The Body is scrollable and the Sticky bottom remains sticky at the bottom of the device screen. This layout is perfect for long paywalls to make the Call To Action always visible on the device even when the user scrolls down.

New layouts will be made available in the next few weeks/months.

Surfaces

A layout is composed of 1 or several surfaces which are displayed in Bold in the Screen structure.

Components can be dragged and dropped in the surfaces and reassigned from one surface to another one. Within a surface they can be reordered.

Components that haven't been assigned to any surface can be found in the Unassigned folder.

You can change the layout even after configuring the components, and reassign them to the different surfaces available in the new layout.

When changing layout, all the components are put in the Unassigned folder and you must reassign them one by one to the surfaces of the new.

By clicking on a surface, you can change its properties, such as its background and the padding

Padding and margin

Padding and margin can now be adjusted with the Screen Composer. It provides you with much more flexibility to tailor your design as you desire.

Padding is the space inside a component, between its content and its border. It adds space around the content within the element. It can be defined for surfaces and components.
Margin is the space outside a component, separating it from other elements. It adds space between the component's border and the surrounding elements. It can be defined only for components.

Both padding and margin control spacing but in different contexts: padding is inside, margin is outside.

Library of components

The Screen Composer features a comprehensive list of components which can be customized in many different ways. Here is the list of components available today:

New components will be integrated in the next weeks and months.

Here are the capabilities offered by each Component

Various features associated with the Screen composer

Adapting Screens to different devices

Localizing your Screen

Previewing your Screen on the device

Importing your custom fonts

Configuring a Screen with the Screen Composer (NEW)

General overview

🚧
Retro-compatibility considerations and fallback Screen for old versions of the SDK

📘
Is this possible to migrate legacy Screen in the new Screen composer?