Conventions evolve with platforms and need periodic review

What it is

Interaction conventions evolve as operating systems, device forms, input methods, accessibility capability, service models, and user experience change. An icon, gesture, navigation pattern, or privacy cue that was broadly understood may gradually lose shared grounding; an emerging practice may not yet be stable. Convention review is the continuing process of checking whether external expectations a design relies on are still recognized by target users and fit the present task.

Why it happens

Convention depends on repeated exposure, and platform updates, market migration, and social practice change what people encounter repeatedly. New devices introduce new possible actions; old controls may no longer work for screen size or assistive technology; evolving safety and privacy expectations reshape what counts as reasonable operation. If a product freezes an old pattern as unquestionable, the gap between user experience and interface gradually widens into discovery failure, erroneous transfer, or lost trust.

Studying it

Periodically inventory the external conventions behind frequent and consequential interactions. Use platform-release change, target-user research, support records, and task data to judge their stability. Compare understanding and success across user groups, devices, and versions, recognizing that newcomers and long-time users may have different expectations. Test proposed changes in limited scope or staged release to validate migration between old and new convention.

Where it stops holding

Evolution does not mean chasing every short-lived trend. Stable, effective, target-user-understood patterns should not be replaced merely because visual fashion changes; frequent change itself creates transfer cost. Yet waiting until “everyone has changed” can leave a product behind for too long. The purpose of review is an evidence-based decision about when to retain, provide compatible transition, or update deliberately.

Applying it

• Maintain a convention inventory for key interactions that includes platform dependency, target population, last validation date, and risk level.
• After significant platform or device changes, prioritize review of input, navigation, state expression, permission, and accessibility conventions.
• When updating, retain recognizable anchors, provide migration explanation and recoverable paths, and use data to confirm that an old pattern can safely retire.

Related

• Same group: B2.11.1 Conventions come from broad exposure rather than inherent correctness · B2.11.2 Departing from convention must be significantly better to be worthwhile
• Nearby: B2.10.2 External consistency means consistency with platforms and similar products · B2.10.3 When consistency conflicts with optimization, evaluate transfer cost
• Search terms: evolving convention · platform evolution · pattern review