Step 1 of 6
Define onboarding steps and data
Decide exactly what to ask, why, and where each answer lives.
Define the onboarding spec. List 3-5 steps, each with: the single question/decision, the input type, validation rules, whether it is required, and the exact profile field it writes to. Add an onboardingCompleted flag and onboardingStep pointer to the user model. State how each answer will personalize the app (at least one concrete use per answer).
Expected after this step
A step-by-step spec with fields, validation, and personalization uses.
Should not happen
- ✕A pretty wizard whose answers are thrown away
- ✕Users stuck in onboarding loops after completing it
- ✕Refresh restarting the wizard from step one
- ✕Skip buttons bypassing required data
Verify before continuing
Do not move on until every check is true. The complete button stays locked until then.
Do not continue if…
- !A pretty wizard whose answers are thrown away
- !Users stuck in onboarding loops after completing it
- !Refresh restarting the wizard from step one
- !Skip buttons bypassing required data
If the AI messes this up
Use this when the AI fakes progress or breaks the feature. It forces a real fix.
Steps collect data with no stated use. For every question, name where the app will use the answer - or cut the question.