F1.14.4minting a conventiondesign

A new convention takes long, consistent exposure before it holds

Aliases: consistent exposure · new spatial habit · product-level convention

What it is

“Swipe up for the next” in short video became a command because the same gesture in the same place was repeated for years, by one product and then a class of products, with almost no counter-example. A new app that wants “pull down from the top to close”, or “that odd shape at the lower-right means publish”, cannot write the slot with one onboarding screen. Minting a convention takes the same mapping, across sessions and surfaces, for a long time, without the product changing its mind in between.

An onboarding motion can be seen once. Seen once is not a convention. A convention is a first landing that still hits after the onboarding has been dismissed.

Why it happens

A new slot falls from controlled search into a motor program through massed repetition under consistent mapping. Platform-level conventions already occupy the sweetest slots; a product-level convention is competing with those statistics. There are two ways to compete: pick an empty slot the platform has not written (a mid-edge, a particular gesture) and occupy that same slot on every surface the command appears; or accept a long minting period and, during it, keep a second path that matches the platform.

Changing one’s mind is the main way minting fails. Lower-right is Publish in Q1, a campaign entry in Q2, Publish again in Q3 — the repetition is zeroed, and search never drops into automatic. Fighting a platform convention (close at the lower-left) puts every exposure in a fight with stronger statistics, and the minting period approaches never.

Where it stops holding

Internal tools, small populations, professional software used many hours a day, can mint faster: repetition is dense, and consumer platform chrome is not competing as hard. One-shot campaigns and seasonal entries have no “long”; they should borrow an existing convention, not invent a slot. A convention that holds on one page and still follows the platform on every other page will be filed as a special case of that page, and will not travel. Assistive-tech users may never reach the new slot (a gesture, an edge); minting has to ship a path that does not depend on the new slot, or those users are locked out of the convention.

Applying it

  • Write the slot to be minted as a cross-surface list: every page where the command appears occupies the same place and the same gesture, and versions do not change their mind.
  • During minting, keep the platform path (still closeable at top-right, not only by a pull-down). The new slot is an accelerator, not the only entry.
  • Do not let one onboarding screen stand in for repetition. The first real task after onboarding is dismissed is where you see whether the slot has started to be written.
  • How to check: people who have used the product for two weeks or more and have not seen onboarding in the last week, on an unprompted page, perform that command. A first landing on the new slot means minting has started. A first landing still on the platform slot, then a miss, means the new slot is still something they saw once in onboarding.

Related

  • Same group: F1.14.1 Positions acquire fixed meanings through long use, such as top-right for close or more · 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
  • Nearby: F1.06 Positional stability of frequent actions · F1.05 Edge and corner accessibility
  • Search terms: minting a convention · consistent mapping · spatial habit

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/F1.14.4