Lag caused by latency is perceived as stickiness
Aliases: stickiness · touch latency · directness
What it is
When content follows a finger rather than moving synchronously, people often perceive latency lag as stickiness: an object seems held by resistance, needs larger motion to catch up, or slowly arrives after the hand stops. This is a subjective control-loop mismatch, not merely unsmooth animation.
Why it happens
Visual position trails proprioceptive position, so people increase speed or travel to compensate; the display responds later, producing chasing, overshoot, and repeated correction. There is a counterintuitive point here: a constant small delay is something the motor control system can adapt to fairly well — much like people adapt to a game controller with slightly slow response, as long as the lag is the same every time, the brain can learn a stable compensation and lead its motion slightly to cancel it out. What actually produces this irregular, ungraspable "sticky" feeling is frame-time jitter: when the delay itself varies unpredictably from moment to moment, the relationship between finger and content is different every time, the motor system has no stable value to learn and adapt to, and each correction risks applying the wrong amount of force — it looks like the content is "stuck" to the finger, alternately loose and tight, rather than simply running a beat behind.
Studying it
Compare stable delay, variable delay, dropped frames, and refresh rate through drag paths, braking error, corrections, and subjective sticky/direct ratings. Use blind or randomized conditions so known performance labels do not bias experience judgment. One targeted comparison holds the total average delay fixed and varies only its variance — if a condition with the same mean latency but higher variance is rated noticeably "stickier," that confirms jitter itself, not the mean delay, is the main driver of the sticky feeling.
Where it stops holding
Easing or intentional damping can feel heavy without being input latency; distinguish content physics from direct manipulation. A concrete test that separates the two watches what content does once the finger stops moving: genuine input latency only lets content catch up and settle within a short window after the finger stops (roughly one display refresh cycle); if content keeps sliding or decelerating for a noticeably longer stretch after the finger is completely still, that is a deliberately designed damping or inertia model at work, and it should not be misdiagnosed as a latency problem and sent down the performance-optimization path.
Applying it
- Reduce latency spikes and frame-time variance during gestures, not average frame rate alone.
- Keep directly dragged objects close to touch, moving decorative animation to secondary layers.
- Accept with real drag and docking tasks plus subjective directness, not a performance dashboard alone.
Related
- Same group: C2.10.1 Drag directness requires end-to-end latency below a perceptual threshold · C2.10.3 Predictive compensation overshoots when direction changes abruptly
- Nearby: D1 Output and feedback channels · C2.07 Touch-down and touch-up activation
- Search terms:
touch latency·stickiness·direct manipulation