Platform Overrides help you decide when to adapt patterns for specific platforms, such as iOS, Android, or Web. While most of your system should stay consistent across platforms, overrides give teams the flexibility to respect native conventions, accessibility standards, or technical limits. This tactic balances consistency with usability by clarifying where to stay aligned and where to intentionally diverge.
How to
-
Start with the base system Use outputs from your Audit to identify the core tokens, components, and patterns that should remain consistent across platforms.
-
Identify override triggers Look for platform-specific needs such as: • Native UI conventions (e.g., iOS navigation vs Android tabs) • Accessibility requirements (touch targets, motion, keyboard focus) • Technical or performance constraints • User expectations unique to the platform
-
Decide when to override Agree criteria for when an override is justified versus when consistency should win. Document decisions in your Guidance Setup so teams know what is standard and what is exceptional.
-
Apply and document overrides Create clear specifications that show both the shared base and the platform-specific variation. Where possible, link directly to specs so overrides are easy to find and implement.
-
Review consistency Run periodic QA Review or Accessibility Review sessions across platforms to ensure overrides are still valid and not creating unnecessary drift.