In this article, we focus on guiding users through different navigation paths in your iOS or Web2App onboarding sequence, specifically based on their selections from screens with a picker type.
It's crucial to understand that pickers are designed for users to select from predefined options. These options can handle various input types, such as String, Integer (Int). However, for setting conditions for user segmentation, these inputs need to be "Int" type.
Let's consider a scenario where you ask users to select their year of birth from a picker and wish to segment them based on this choice. Here's how this can be implemented:
Suppose you have a picker where users can select a year, and you want to direct users who pick the year 1992 to a specific path, say way1. Similarly, if a user picks the year 2000, you would navigate them to way2. Any user who selects a year other than 1992 or 2000 will be directed to way3.
To configure user navigation based on these specific selections, you will need to establish three distinct connections, two of them governed by a conditional statement using the "==" operator:
In your iOS or Web2App onboarding users will be segmented accordingly:
If you want to navigate all users who didn't pick the year 1992 to way1, and all other users will go to way2.
To configure user navigation based on this rule, you will need to establish two distinct connections, one of them governed by a conditional statement using the "!=" operator:
In your iOS or Web2App onboarding users will be segmented accordingly:
You could segment users who pick years FROM 1992 TO 2000 and navigate them to way1. All other users (those who pick years other than between 1992 and 2000) would navigate to way2.
To configure user navigation based on this rule, you may establish two distinct connections, one of them governed by two conditional statements using the ">" and "<" operators (in that case, 1992 and 2000 will not be included in way1) or the ">=" and "<=" operators (in that case, 1992 and 2000 will be included in way1).
Here, we demonstrated how the ">" and "<" operators work:
Setting such conditions, in your iOS or Web2App onboarding users will be segmented accordingly, ensuring that each user’s journey is customized according to their specific choice from the picker.
