Continuous mid-air control needs a live stream of feedback, not a bell at the end

What it is

Pinch-and-drag, painting an in-air slider, walking with an object—these actions are a stretch of time, not a hit. Feedback has to walk with them: where the object is now, whether tracking dropped, what the gain is. Saying “done” only on release is driving the whole road with eyes closed. Endpoint error, mid-path drops, and tremor stay hidden until the end. A discrete click can close on one pulse. Continuous control cannot. Contact dragging has surface friction and the object moving under the finger. Mid-air takes both away and leans harder on a continuous visual or haptic stream.

Why it happens

People use feedback error to change the next hundred milliseconds. Continuous control is a servo, not an open-loop throw. An end bell is a settlement, not a servo error. Without friction damping, the hand path shakes more than on glass, so the servo needs to see the object following. If a drop (tracking loss, false pinch-release) is announced only at the end, people finish a path that already went wrong. Delay turns the servo into oscillation: the hand chases a lagging object, the object chases the hand. So a continuous substitute is not merely “there is feedback.” The feedback must be sampled as often as the hand.

Studying it

Tasks: drag to a target, or track a moving path. Conditions: end-only cue, low-frame follow, high-frame follow, follow plus instant drop cues. Measures: endpoint error, extra path length, whether people stop after a mid-path drop, oscillation count. Sweep feedback delay from 0 to 200 ms and watch when error steepens. Control with touchscreen drag. Do not claim continuous feedback is sufficient from a discrete-click task.

Where it stops holding

A very short continuous (a flick of a drag, under 200 ms) is almost discrete; an end cue may suffice. A fully open-loop ballistic swipe is not a servo; live following makes people aim at the feedback instead of finishing the throw. In networked collaboration, follow delay is dominated by the network; local high frame rate will not save it—predict, or degrade to discrete steps. If the hand occludes the visual follow, continuous feedback is nothing; draw the object beside the hand or change channel.

Applying it

• On continuous manipulation, the object moves when the hand moves, and drops are cued on that frame. Ban a check-mark only on release.
• Put follow delay in the budget. If drag error steepens with delay, do not do continuous mid-air control on that link.
• Accept with drag-to-target plus one mid-path occlusion: do people stop at once, or finish the drag and then discover the object did not follow.

Related

• Same group: C4.11.1 Mid-air gestures have no natural contact feedback · C4.11.2 In-range, locked, and fired must be separately legible · C4.11.4 Primary states need at least one non-visual channel
• Adjacent: C4.06 Air pinch · C1.08 Drag and drop
• Search: continuous feedback · control-display lag · mid-air drag