Skip to main content
All CollectionsOnboarding.Online FAQCreate & Manage onboarding
How to make your iOS onboarding published (available for your users). Onboarding lifecycle and statutes
How to make your iOS onboarding published (available for your users). Onboarding lifecycle and statutes

Brief discussion on what for and how to change the onboarding statuses, get them tested and published in the app

L
Written by Leanid Yuryeu
Updated over a week ago

When you have finished designing and setting up your onboarding, you can make it available for testing in your iOS application and publish it for users in the version available from the AppStore.

Each onboarding has its status, which indicates the stage it is at. You can check the onboarding status on the page with the list of onboardings of your project (menu option named "Onboardings") in the column "Status:"

How to change onboarding statuses and what they mean:

"In Development."

As soon as you create a new onboarding, it automatically receives the status "In Development," which means you can freely continue to set up the chosen design theme, create onboarding screens, and establish or edit connections between screens. Onboarding can be corrected at any time by the users you have invited.

"Ready for QA."

As soon as you finish setting up and editing the onboarding, the next step is to publish it to QA. For this, you need to press the "Publish to QA" button on the main onboarding Flow panel, where you work with the screens and their connections.

Before publishing, ensure that:

  • Your onboarding flow has a designated First screen.

  • All screens in the sections have uninterrupted connections.

  • Ensure that your onboarding will visually and functionally align with a range of iPhone models with the screen preview feature

⚠️Please note that the "Publish to QA" step is inevitable, as it is built into the visual constructor to protect your project from errors in the released version. We recommend using it to avoid bugs and manual errors. But you can skip it by pressing "Publish to Prod" directly.

After pressing 'Publish to QA', a pop-up window will appear asking for confirmation to publish this version to QA. You can continue the action by pressing "Yes" or cancel it by selecting "No."

After confirming the publication and its completion, you will see a notification of the successfully published onboarding in QA.

After that, the onboarding status will change to Ready for QA on the main onboarding control panel of the project. This means that the onboarding is available for internal testing.

📢 NOTE: In the version of onboarding with the status "Ready for QA," changes are not possible. To make any changes, you need to clone the onboarding and continue further settings. 📢

Please see the visual how to clone the onboarding here in this article.

"Released on Production."

As soon as you test your onboarding you can make it visible to the users of your iOS app from the AppStore, and publish it by pressing the "Publish to PROD" button.

After pressing 'Publish to Prod', a pop-up window will appear asking for confirmation to publish this version to Prod. You can continue the action by pressing "Yes" or cancel it by selecting "No."

After confirming the publication and its completion, you will see a notification of the successfully published onboarding in Prod.

After that, the onboarding status will change to Released on Production on the main onboarding control panel of the project. This means that the onboarding version is available to users of your iOS app from the AppStore.

Important:

📢 As with the QA stage, the version in the "Released on Production" status cannot be edited or deleted. You can only clone it for editing.

📢 To replace the current onboarding in the "Released on Production" status, simply publish a new one using the steps described above. After that, the status of the first onboarding will be replaced with "Removed from Production".

For more information on publication, cloning, and avoiding potential issues during the release, it is recommended to consult the frequently asked questions section.

By understanding these stages and statuses, you can effectively manage the onboarding process, ensuring a seamless and error-free experience for the users of your application.

Did this answer your question?