Pattern model
Parts that must work together
Category navigationSetting label and descriptionControlDependencySave or immediate feedbackDefaults and recovery
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
Does change apply immediately?
Use immediate controls only when feedback and rollback are reliable; otherwise provide an explicit save model with unsaved-state protection.
How are settings grouped?
Group by user goal and consequence rather than internal service ownership or implementation architecture.
What depends on what?
Explain disabled controls and reveal dependencies without causing layout shifts or hidden side effects.
Cross-system baseline
End-to-end accessibility
- Use headings and field groups
- Keep labels stable as values change
- Announce save failure
- Support zoom and long descriptions without separating controls
Common mistakes
Failure patterns to test
01
Mixing account policy with personal preference
02
Changing labels from Enable to Disable
03
Autosaving without failure handling
04
Hiding destructive account actions