Onboarding
Help new users get set up and reach their first useful action in your app.
Onboarding introduces your app and helps people start using it. Build it as an Experience to explain what the app does, collect preferences, and give users a next step based on their answers. You can update the questions and screens as you learn what helps people get started.
Create onboarding
Start a Task and describe the introduction, the questions, and where users should go afterward:
Create onboarding for a running app. Ask for the user’s goal and weekly availability, explain how the plan works, then open their first workout. Beginners should see an extra introduction.
Nuxie creates the screens and connects them. Open the Experience’s Canvas to change the content, arrange the screens, or select a step’s settings. If the last step opens a feature in your app, connect it to the corresponding App Action handler in your SDK integration.
Questions and answers
A response collection holds the answers from onboarding. Attach one to a screen with Add capability → Response, then bind each input to the field it updates.
For a running app, you might use a single-select goal for what the user is training for, a number field for weekly_sessions, and a multi-select training_days for their availability. A text field such as notes gives them room to add anything else.
Open Responses → Fields to configure the collection. Connect the goal options to goal, the session count to weekly_sessions, and the training-day choices to training_days. You can ask Nuxie to make these connections in the Task. See Data and bindings for a worked example.
Add Submit response after the final answer to mark the answers as submitted. For example, the Continue action on your summary can submit the answers before opening the first workout. Navigating between screens alone doesn’t submit them.
Personalization and branches
Answers can change both the content and the route through onboarding. A summary can use goal to show the chosen plan, while a condition can give beginners an extra introduction.
If a question is optional, include a skip path and a fallback for any content or condition that uses its answer. A back action lets users change earlier answers; later steps use the current answer when choosing the path.
Open the next step in your app
Use an App Action to hand the selected goal and availability to your app. Ask Nuxie to add it after submission:
After submitting onboarding, run start_workout with goal, weekly_sessions, and training_days in the payload. Then close the Experience.
Your app’s handler uses those values to create or open the workout. It needs to recognize the same action name and payload fields. Run App Actions covers the iOS handler; see your SDK reference for other platforms.
The saved answers remain available in Collected responses, independently of the work your app performs with them.
Audience and re-entry
Choose an entry event, such as account creation, and an audience for onboarding. When the setup belongs to a signed-in account, identify the customer before sending the entry event so Nuxie evaluates delivery for that account.
Use re-entry settings to decide whether someone can start again. First-time setup and a repeatable tutorial may use similar screens, but need different audience and frequency settings. Sending the event asks Nuxie to evaluate delivery; those rules still determine whether the user can enter.
Conversion goal
The goal is what you want someone to do after getting set up. For a running app, that might be workout_started. Configure that event as the conversion goal, choose an attribution window, and have your app send it after the workout starts.
This lets you distinguish finishing onboarding from reaching value in the app. Response submission records the answers, leaving the final screen ends the introduction, and the goal event records the action it led to.
App integration
Use Preview to enter answers and try the different branches, including skipped questions. The Run Log shows which steps were taken if the route differs from what you expected.
In your installed app, try onboarding as a new user and as a returning user. This also exercises delivery, the final App Action, and any use of collected answers by the app. See Testing in your app for identity and delivery setup.
Results
Measurement brings together Journey starts, responses, and conversions. If users leave before submitting their answers, look at the questions and the path to submission. If they finish onboarding but rarely start a workout, look at the handoff into the app.
Use Experiments to compare a shorter path, different questions, or another introduction. Keeping the same conversion goal lets you compare which version helps more people take that next step.