Positions acquire fixed meanings through long use, such as top-right for close or more

What it is

A never-seen app opens and the hand is already at the top-right — that is where close or more “should” be. The label does not have to be read first; the place carries the command. A positional convention is long, cross-app repetition writing a slot into a meaning: top-right on iOS and much of the Web dismisses this layer, top-left goes up a layer, near bottom-centre is the primary. People do not search the chrome with their eyes for a glyph each time. They ask the slot, then look at what is in it.

Top-right is only the hardest example. Rightmost on a tab bar, leftmost on a desktop menu bar, the primary at the lower-right of a dialog — the same kind of slot written into the hand.

Why it happens

Place is an extremely stable retrieval cue. After a few thousand “leave this layer → top-right”, slot and command bind as a motor program; labels and glyphs become a check, not the start of search. This is not remembering “Bold is third” inside one product. A convention is cross-app, cross-session, from statistics a platform community shares, not from one version of a toolbar.

Once a slot is written as meaning, empty still means. Put nothing at the top-right and people still tap, hitting whatever happens to sit in that neighbourhood; or they hesitate, because the command “leave” cannot find the address it is owed.

Studying it

A population-stereotype questionnaire: no labels, only a map of empty slots, “where would close / back / primary / more sit?” Then, on an unseen UI, have people perform those commands and watch the first landing.

Independent variables: platform experience (iOS / Android / desktop), whether the slot matches that platform, whether a glyph is present. Dependent variables: first landing, time to find the target, taps on “whatever command now occupies that slot”.

Report cross-platform users separately, or two conventions average into a slot neither community owns.

Where it stops holding

New users who have never touched the platform have no such slots; place carries no command, and glyph plus words have to speak. Games and creative tools often refuse platform chrome on purpose, conventions are weak, and top-right cannot be trusted to close. Speech and shortcuts do not use slots. The same hand switching iOS and Android in one day will contaminate the two slot-sets, and first landings will cross platforms.

Applying it

• Close, back, more, primary occupy the slots that platform has already written. Do not move them to the opposite side for visual symmetry.
• If top-right is not close or more, do not park a similarly tappable control there that will be taken as leave.
• An empty convention slot is allowed; a command of opposite meaning in that neighbourhood (Confirm payment at top-right) is not.
• How to check: skilled users of that platform, glyphs and words masked, layout only, “where is close, where is back?” A wrong slot is not a badly drawn icon. The place has not yet joined this convention.

Related

• Same group: F1.14.2 Putting things off the platform convention raises search cost · F1.14.3 Conventions follow platform and writing direction; they cannot be copied globally · F1.14.4 A new convention takes long, consistent exposure before it holds
• Nearby: F1.06 Positional stability of frequent actions · F3.09 Position and hierarchy
• Search terms: positional convention · population stereotype · close button