J3.05.1single pointerdesignresearch

Multipoint gestures need a single-pointer alternative

Aliases: pinch alternative · multipoint alternative · one-finger operation

What it is

Pinch-to-zoom, two-finger rotate, three-finger swipe — these gestures require more than one contact at the same time. For someone who can sustain only one contact (one hand, a mouth stick, some head pointers, some switch mappings), the gesture does not exist. The criterion: there must be another path that uses only a single point. Single point means one contact, one click, or one activation. A second finger does not have to be present.

This leaf only asks whether the alternative exists. Whether it is easy to find, or whether it costs many extra steps, belongs elsewhere.

Why it happens

Multipoint is a concurrency constraint: two contacts must overlap in time. Motor control, missing digits, grip, and assistive hardware all make concurrency impossible. When the system maps a switch onto “move pointer + activate”, there is also only one pointer at a time. Trackpad multipoint is equally closed to someone who has not enabled it, or who has AssistiveTouch set to a single point.

If a product hangs a function only on multipoint (a map that zooms only by pinch, a canvas that rotates only with two fingers), the function is gated on concurrent contact. A button, a slider or a stepper opens the gate — not because the button is more elegant, because a single-point path now exists. Without that path, keyboard access will not rescue the function in a touch setting either.

Studying it

List every multipoint gesture and the function it binds. For each, ask: with multipoint disabled (or with only one finger), can the same function complete. The answer is only yes / no. Do not score the alternative’s usability at this step.

Devices: phone touch, laptop trackpad, external pointer. Two-finger zoom on a trackpad and pinch on a phone may be two multipoint realisations of one function; confirm each has its own single-point exit.

Where it stops holding

OS-level multipoint (system task switch, system zoom) is outside what an app can replace; the app owns functions it bound itself. Professional tools that need fine continuous control may keep multipoint as an accelerator, but the same result must still be reachable with single-point controls — even if slower. If the “function” of a gesture is to teach pinch itself, an alternative is meaningless. Games that use two fingers to shoot and aim at once still need single-point remapping or aim assist; genre is not a waiver.

Applying it

  • Inventory pinch, two-finger rotate, three-finger swipe and kin. Give each bound function a button, slider or equivalent single-point control.
  • Do not only mention “you can also use a button” in help copy while omitting the button. This leaf first requires that the control exists and can complete the function.
  • How to check: with one finger only (or with multipoint gestures off), complete zoom, rotate and page switch. Any step that needs a second finger has no single-point alternative.

Related

  • Same group: J3.05.2 Path-based gestures need a non-path alternative · J3.05.3 Dragging needs a click alternative
  • Nearby: J3.11 Path-based gesture alternatives · J3.07 Drag alternatives · J5.05 Switch and eye-gaze input
  • Search terms: single pointer · multipoint gesture · pinch alternative

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/J3.05.1