Gestures depend on recall rather than recognition
Aliases: recall-based command · gesture memory · recognition vs recall
What it is
A menu lets people recognize among visible options. A gesture asks them to recall a pairing of stroke and command onto a blank surface. When Nacenta and colleagues compared memorability of pre-designed and user-defined gestures, they were measuring this load: not “can you find that a gesture exists,” but “knowing it exists, can you retrieve the motion.” Discoverability is about existence; memory load is about retrieval.
Why it happens
Recognition has external cues: a label, an icon, a location. Recall must keep arbitrary pairings such as “three fingers left = back” in long-term memory, and the interface offers no prompt for that pairing at retrieval. Arbitrary maps cost more to encode than metaphoric ones; even self-chosen strokes still require recall after a delay, not re-recognition. Working memory must also hold the stroke shape during performance; one wrong direction becomes another command. Buttons spread options out; gestures hide them inside the user’s head.
Studying it
Train to stable reproduction, then probe specified commands with no hints. Record accuracy, a confusion matrix, and retrieval time. Delayed retest and user-defined versus designer-defined contrasts, as in Nacenta et al., are usable paradigms. Factors include self-definition, semantic metaphor, and set size. Do not draw a gesture chart on the test UI—that turns recall into recognition.
Where it stops holding
Manipulation that is isomorphic with the world (content follows the finger) barely uses recall; that is continuous control, not a command gesture. A daily back swipe migrates into procedural memory and the load drops. The same stroke with different meanings across apps turns recall into interference. High memory load is not the same as never having discovered the gesture; someone can recognize a diagram in help and still fail to produce it in place.
Applying it
- Keep unusual commands in menus; reserve gestures for frequent, strongly metaphoric actions.
- Put weak recognisable cues at the point of use (a directional remnant, a handle) to cut pure recall.
- Accept by delayed, diagram-free reproduction, with per-command confusions, not a single “how much was remembered” score.