C3.15.2Pull-to-refresh threshold crossing feedbackdesignresearch

Crossing the trigger threshold needs feedback

Aliases: release to refresh · refresh threshold · armed pull

What it is

Downward overscroll has a distance threshold: lift past the line actually requests; lift short of it only rubber-bands. The instant of crossing must be perceptible—an icon flip, copy changing from “keep pulling” to “release to refresh,” a haptic—or people cannot tell whether lifting now cancels or commits. Feedback binds to the crossing, not to the spinner after lift.

Why it happens

The threshold cuts continuous overscroll into “still previewing” and “armed.” With no phase cue, people guess whether they have pulled enough, so they overshoot far or lift a few pixels short. Crossing feedback must reverse: pull back below the line and copy and icon return to preview, so they know this lift will not request. A spinner that appears only after lift is a loading state, not a threshold state; using loading to impersonate the crossing leaves people blind while still down. Damping can rise slightly near the threshold so crossing has a bite, but the bite must not lock them from pulling back.

Studying it

With crossing visuals/haptics on or off, the task is “pull to the just-refreshable point, then decide to cancel or commit.” Dependent measures include successful cancel after crossing, commits that never crossed, and error of overscroll distance relative to the threshold. Eye tracking shows whether people hunt for a cue near the threshold. A negative control that always says “release to refresh” should drop cancel rate.

Where it stops holding

Reduced-motion settings may kill the flip animation; the crossing then needs static copy or a haptic. Devices with sound and haptics off have vision only. When the threshold is a nonlinear function of pull damping, a fixed “line” drawn in pixels will sit off the real fire point; the line must follow the arming function, not the pixels.

Applying it

  • On crossing, change copy or icon heading, optionally with a short haptic; pulling back under the line restores preview. Show a spinner only after lift, and only if armed.
  • Do not send the refresh request before the line is crossed.
  • Have people pull to “where you think it will just refresh” and hold, and ask whether lifting now will request. The verbal judgment should match system arming. Then cross and pull back to cancel. If cancel still sends a request, the crossing was not reversible.

Related

  • Same group: C3.15.1 Pull-to-refresh attaches to overscroll at the top of a list · C3.15.3 Conflicts with sticky headers and search fields · C3.15.4 The gesture becomes redundant under auto-refresh
  • Adjacent: C3.07 Pan · C3.03 Long press
  • Search: release to refresh · threshold feedback · armed state

Cards in the same group

Quick Actions

Share

Share this page

ios_share

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