Meeting user expectations.
WHY IT MATTERS
Users know their platform, and an application that ignores its conventions feels wrong.
WHAT DIFFERS BETWEEN PLATFORMS
Navigation patterns and where back lives Typography and default components How settings and sharing work Icon style Where primary actions are placed
WHAT TO FOLLOW
Each platform's guidelines, where they differ.
WHAT THAT COSTS IN CROSS-PLATFORM WORK
Conditional interface code.
WHAT TO DECIDE
Whether brand consistency or platform familiarity matters more.
WHAT THE USUAL ANSWER IS
Platform familiarity for interaction, brand for identity.
WHAT THAT MEANS PRACTICALLY
Your colours and typography, their navigation and controls.
WHAT TO NEVER IGNORE
The system back gesture Safe areas, around cut-outs and rounded corners System text size and accessibility settings Dark mode
WHAT REVIEW MAY REJECT
Interfaces imitating system interfaces misleadingly Applications not respecting platform navigation
WHAT TO READ
Both platforms' published design guidance.
WHAT TO TEST
With users of each platform.
