Pattern model
Parts that must work together
Entry contextValue framingRequired setupProgressSkip and returnFirst meaningful outcome
Why this matters
A pattern is not a screenshot. It is a reusable decision model that must preserve intent, state, recovery, and accessibility as layouts change.
Decision framework
Questions to answer before choosing UI
What is truly required?
Defer preferences and education that do not block first value. Explain why any required setup exists.
Should guidance be staged?
Introduce concepts when the related feature appears rather than front-loading a complete product tour.
How can people return?
Make skipped education, examples, and setup available later from the relevant product context.
Cross-system baseline
End-to-end accessibility
- Do not force a visual tour through hidden context
- Support keyboard and screen-reader navigation
- Avoid focus traps across coach marks
- Preserve progress and allow exit
Common mistakes
Failure patterns to test
01
Blocking the product with optional questions
02
Long carousel tours
03
No skip or return path
04
Celebration motion that ignores preferences