Follow existing platform conventions
Aliases: platform standards · system conventions · industry standards
What it is
Interfaces should follow placement, gestures, control behavior, shortcuts, and status expressions already established by the target platform, industry, and accessibility standards. A platform convention is a default expectation users import from other applications; following it means the user is not learning a new rule, only confirming that this product has not broken a rule they already know.
Why it happens
Platform conventions are trained by countless applications and system surfaces: back direction, close placement, zoom gestures, date pickers, menu semantics, and focus order have become habits users no longer think about. Violate one and the user tries the old habit first, searching for a new rule only after it fails; on urgent or frequent paths, that failure repeats, because a habit does not vanish after failing once. Accessibility standards additionally let assistive technology interpret the interface through a predictable model — screen readers depend on exactly this stable mapping between control behavior and platform role semantics.
The strength of a convention is not fixed; it depends on two things: how many other applications trained the user into it, and whether the operating system itself has since revised it. The same gesture carries different strength for different users — someone who has only used devices with a physical back button and someone who has only used gesture navigation hold entirely different default expectations for "back." OS generational changes also shift conventions outright: once navigation moves from a physical button to a gesture bar, the old convention is no longer the platform's convention, and continuing to follow it becomes the new deviation. This is why "follow platform conventions" cannot mean following a list frozen at some point in time — it means following whatever expectations the current user population actually carries, and that list needs periodic reverification against OS versions and user cohorts.
Studying it
Expectation testing can establish whether a location or gesture has become a convention: show users a static screenshot or low-fidelity prototype with no real interaction, ask "what happens if you tap here" or "what do you think this gesture does," and compare their predictions against actual platform behavior. First-click testing works too — have users who know the platform but have never used the product attempt a task, and record the gap between where they click and where the real control sits; clusters of deviation usually mean a custom design has collided with a strong convention.
For shipped products, heuristic evaluation applies: have several evaluators familiar with the target platform's design guidelines independently review every screen, flag deviations, score them, and then merge results and compare disagreements. Independent scoring by multiple evaluators controls for the evaluator effect — on the same interface, different evaluators miss or misjudge different deviations based on their own experience, so a single evaluator's conclusion cannot be trusted on its own.
Where it stops holding
Conventions are not law; obsolete or inaccessible patterns should be replaced, and brand or task innovation may require a different mode. What matters is that any deviation have a reason, be discoverable and learnable, and carry textual redundancy on critical paths rather than relying on an icon alone. A cross-platform product should not force one platform's convention onto another; it should share concepts while letting the interaction branch.
Internal enterprise tools are a concrete counter-case: if a user population has spent years trained by an internal system into a habit that diverges from the OS convention — say, an industry tool that has long used left-click-drag to mean copy — conforming to the general OS convention would actually disrupt deeply ingrained muscle memory. Here the "convention" should follow that population's historical usage rather than the system-level guidelines, but the design documentation should state plainly that this is a deliberate exception, so a later team does not mistake it for an oversight and "fix" it away.
Applying it
- Maintain a platform-convention inventory covering navigation, gestures, close/confirm, files, dates, keyboard, and focus order; note the OS version used when each entry was verified, and recheck it after OS updates.
- Use native controls or equivalent behavior by default; supply keyboard, touch, voice, and accessibility states for any custom controls.
- When deviating, retain a positional anchor, guidance, and a recovery path, and record the reason, the applicable version, and the scope of the exception.
- Run first-click tests with users who know the platform but not the product, measuring the gap between click targets and real control locations; where deviation clusters appear, check first whether the "convention" was misjudged before rushing to "educate" the user.