Long-press and multi-click on one key raise cognitive load

What it is

One key: click is Back, long-press kills the app, double-click opens history—several commands on the same piece of plastic. Before pressing, the user has to choose which press shape this is, and while pressing, whether the threshold has been crossed. Long-press and multi-click multiplexing raise cognitive load because saved key positions are swapped for mode memory and timing. Errors land on a different, often irreversible, command.

Why it happens

Click is the default. Long-press waits before forking from click; during that wait the user does not know which the system will take. A short threshold turns intended clicks into long-presses. A long threshold makes people think the key is dead and press again, which becomes a double-click. Double-click needs two downs inside a window; people in a living room press while talking, miss the window, and the second down is another click.

The load is that command identity moves off position onto a temporal shape. Position can be felt; temporal shape has to be remembered, and every vendor’s threshold differs. Long-press on Back kills the app on this box and returns to the system desktop on that one; after a move, the old shape hits a new command.

Multiplexing also breaks feedback. A click can respond immediately; a long-press must not respond before the threshold, or must show “still timing.” Without that, people reconstruct which shape they used from the aftermath, and guess again next time.

Where it stops holding

Power long-press to shut down, volume long-press to repeat, are already stable temporal shapes and the load is negligible—if a third command is not stacked on those two keys. Hold-to-charge in games has an on-screen bar; time is seen, not only remembered. Accessibility “hold to talk” opens a channel while held and stops on release, which is not “hold past eight hundred milliseconds to open another menu.” Mapping OK to “short-press select, long-press open details” in grid browsing systematically mis-opens details, especially with key-repeat on.

Applying it

• Take destructive or irreversible actions off long-press and multi-click; give them a confirm step or their own key. Keep click-on-Back a single meaning.
• If long-press is required, show a cancellable progress immediately on down (a ring on screen, or a remote haptic) and execute only at threshold. Do not wait in silence.
• Do not stack click, double-click, and long-press on one key. At most one temporal shape besides the default.
• Verify by handing the mapping to someone who has not seen this remote, telling them only “this key is Back,” and watching what they do the first time they try to kill an app or open history. If the command only exists as an unstated long-press or double-click, it should not exist as multiplexing. Repeat with key-repeat on, and check whether short presses are eaten as long-presses.

Related

• Within the group: K5.07.1 Limited physical keys should be reserved for the highest-frequency actions · K5.07.3 Interfaces cannot depend on describing a specific key layout · K5.07.4 Voice and trackpad keys are replacing some D-pad operations
• Adjacent: A10.02 Mode errors · K5.01 Focus-based navigation · C6.22 Focus order and keyboard navigation
• Search terms: long press · key remapping · mode error