What users expect.
WHY THEY MATTER
Apple users notice when an application does not behave like the platform.
WHAT THE GUIDANCE COVERS
Layout and spacing Navigation patterns Typography Controls and their behaviour Iconography Motion
WHAT TO FOLLOW
The published guidance for each platform, which differ.
WHAT COMMONLY DIFFERS FROM OTHER PLATFORMS
Where back navigation lives How settings are presented How sharing works Default typography Where primary actions are placed
WHAT TO USE
System-provided components, wherever possible.
WHY
They handle accessibility, dark mode, dynamic type and localisation automatically.
WHAT CUSTOM COMPONENTS COST
All of that, which must then be implemented deliberately.
WHAT REVIEW ASSESSES
Whether the application respects platform conventions.
WHAT IT REJECTS
Interfaces imitating system interfaces misleadingly Applications ignoring platform navigation
WHAT TO DECIDE
Where brand identity applies, and where platform familiarity does.
WHAT THE USUAL ANSWER IS
Your identity in colour and typography; their conventions in interaction.
