C3.20.3Local gesture feedforwarddesignresearch

Local visual previews beat centralized teaching

Aliases: peeking edge · gesture remnant · feedforward

What it is

Discoverability wants cues that live on the object: a peek of action color on a row, a card edge, a drag handle, a short remnant after lift-off. Those pixels sit beside the thing, at the moment of need. Centralized teaching—full-screen overlays, gesture charts in a help center—moves the explanation off the object. Feedforward work such as Bau and Mackay’s OctoPocus shows that a gesture needs to display “what happens if you continue” before the stroke is finished, not in a later lesson.

Why it happens

Recognition is cheaper than recall. A peeking edge makes “more this way” part of the object, so visual search can collide with it. A handle gives a shape that can be tapped or dragged, re-pixelating a zero-pixel command. A remnant leaves a direction in place after a success or a slight overshoot, ready for the next retrieval. Central teaching asks people to suspend the task, store a diagram, and replay it on the object—across working memory. Local cues bind to the object; the task need not switch.

Studying it

Compare three reveals of the same gesture: a full-screen tutorial, a help article, and a peek or handle on the object. The task must be a real goal (archive this, enlarge this photo), not “please demonstrate a swipe.” Measures include unaided success, gaze before the first attempt, and spontaneous use a week later. Dynamic feedforward can also yield a mid-stroke change rate: did the preview make people divert?

Where it stops holding

Heavy cues become noise; lock screens and reading surfaces cannot wear a permanent tint. Games and full-screen media may show handles only when paused. Remnants that linger look like corrupted content. Local preview raises discovery; it does not teach a complex path, and it is not a non-gesture entry. System gestures already carry system cues; a second set from the app collides.

Applying it

  • Leave a recognizable remnant on the object: unread peek, a row handle, a zoom hint at a photo corner.
  • After a slight wrong-way swipe, flash a short remnant; do not launch a full-screen lesson.
  • Test overlay-off, peek-on against tutorial-seen-but-chrome-clean, and compare unaided success.

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.4 A gesture cannot be the only path to a function
  • Adjacent: C3.32 When to teach gestures · C3.05 Swipe
  • Search: feedforward · affordance remnant · peeking edge

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/C3.20.3