A gesture cannot be the only path to a function

What it is

A gesture that experts love still cannot be the only door to that function. There must be a visible, tappable path: a toolbar button, a menu item, a contextual action. The constraint comes from discoverability, not from motor skill—people who never conceive the stroke and people who cannot perform it fail the same way: the function might as well not exist. The pattern matches “add move-up besides drag-to-reorder,” but it covers every command that a gesture fires, not reorder alone.

Why it happens

A visible entry puts the command back in the layout tree, where visual search and assistive tech can collide with it. The gesture then sits on top as an accelerator. If the accelerator is the only path, the product’s function set shrinks for anyone who has not found it. Worse, non-discovery throws no error: there is no failure toast, only “I guess that feature isn’t here,” which analytics records as absent demand. Double-tap to like, a toolbar that appears only after pinch, and three-finger undo without a menu item are this silent shrinkage.

Studying it

Remove the visible entry, then remove the gesture, and compare completion; the number that matters is the gap between gesture-only and button-only, plus how many people declare the function missing. Include newcomers and people migrating across platforms. Do not write “please double-tap” in the script—that disguises a sole entry as already discovered.

Where it stops holding

A purely decorative shortcut on top of an obvious button does not need a second door; it was never the function. System navigation already ships a visible substitute (home affordance, back arrow); apps need not duplicate it, but app-private commands must. Game skill releases that are the operation itself are a different case. The sole-entry ban does not decide whether a taught gesture is later remembered—that is memory load.

Applying it

• List a tappable peer for every gesture command, and make both commit the same model operation.
• In new-user tests, never demonstrate the gesture; a task that can only be finished by gesture is a missing entry.
• Audit release notes that “add a gesture”: if there is no visible entry, demote it to an accelerator or add a button.

Related

• Same group: C3.20.1 Gestures take no screen area, and are therefore invisible · C3.20.2 First-run coaching cannot carry long-term discoverability · C3.20.3 Local visual previews beat centralized teaching
• Adjacent: C3.24 Accessible alternatives to gestures · C3.18 Long-press drag to reorder
• Search: redundant command path · gesture accelerator · sole entry