The custom screen is a unique part of our templates. It can be added at the beginning, middle, or end of the onboarding process.
The distinction of this screen lies in its flexibility: it does not have a predetermined design, allowing the developer to insert any design necessary for you.

Important Points for Testing:

Screen Name:

The name should be clearly defined by the developer in the code and match the name specified in the service.
If the names do not match, the custom screen will be skipped, and the next available screen will appear.

How to Find and Change the Screen Name:

The name is visible directly on the screen and at the top part of the screen after clicking on it.
To change the name, use the edit button in the “Edit screen” section.

Checking Input Labels on the Custom Screen:

Input elements, such as buttons and text fields, can be configured in the service if you want to use user-entered data for user segmentation.

If input elements are not working, ensure that:

The names in the service correspond to the names in the code.
The handling of input elements has been added by your iOS developers in the code.

Checking the Setup of Text Fields and Their Style on the Custom Screen:

You can add any number of text fields (Labels), the content and style of which you can configure and change without a release. To do this, add a Label to the custom screen, enter text, and configure the style. Your developer should set up the processing and position this text on the Custom screen.

If the added label does not display in the app:

Ask the developer to check its processing in the code.
The text in the field for labels should not be empty.
The name of the label in the service should match the name in the code.

Limitations of the Custom Screen:

Theme settings, including background, images, header, and footer, cannot be configured through the service for the custom screen in the iOS app.

The full Checklist with Custom screen is here