Onboarding form
The onboarding stepper is dedicated to onboarding experiences for new users. Its simple design helps users provide key information quickly and seamlessly.
Last updated
The onboarding stepper is dedicated to onboarding experiences for new users. Its simple design helps users provide key information quickly and seamlessly.
Last updated
Within Mirakl, the onboarding stepper should be used:
When a user is setting up an account for the first time
When a user is setting up an organization for the first time
When a seller is creating a store
The onboarding stepper shouldn’t be used:
For standard, sequenced experiences. Use Stepper form instead.
Do not use a datatable within the onboarding layout.
Do not confuse users with mixed topics within a single step; keep one idea per screen.
When asking Mirakl users for information, keep the number of steps to an amount users are able to take in (4 or 5).
Users must fill in their form quickly to secure their arrival on Mirakl. Use standard form components such as fields, select options, checkboxes, etc.
Users need to understand why we're asking for specific information and how we will use that information. Add context and guidance to make the user feel confident.
The onboarding stepper is made of:
On the right side, an illustration picked from the Mirakl library that must be relevant to the overall theme of the form
On the left other side, a form with:
A logo (optional + can be changed at each step of the form)
A title
A progress bar
Form fields
Save/Cancel button group
The onboarding stepper has 2 save modes:
in memory (when the last step is approved)
in the database (save at the end of each step)
You may add an activity loader at the end of your onboarding stepper.
Errors are managed automatically by Roma.
If there are errors within one step of the stepper, the user is automatically redirected to the relevant step.
If there are errors within several steps of the stepper, the user is redirected to the first step where there’s an error.
