Unsupported operation reduces precision and fatigues faster

What it is

Pointing while the whole arm hovers in the air, held up entirely by its own muscles with no external surface to rest on, is called unsupported or mid-air operation — common with standing-height touch walls, in-air gesture interaction, and handheld VR controllers held aloft. Compared to a wrist- or forearm-supported condition, the same person performing the same pointing task unsupported lands with worse precision and fatigues sooner — and these are not two independent effects but two symptoms of the same underlying cause.

Why it happens

Unsupported, the proximal joints — shoulder and elbow — must sustain continuous isometric contraction just to hold the arm up against gravity; this postural-maintenance load itself introduces small force fluctuations that stack on top of the fine control the pointing movement requires. With no fixed anchor, an angular error at any joint along the arm's chain has to be compensated by shoulder-elbow coordination rather than being pinned down, so error amplifies stage by stage to the endpoint. The sustained muscular contraction needed to hold the posture accumulates metabolic byproducts and reduces available motor-unit capacity over time, which is the direct cause of faster fatigue; fatigue then further amplifies the hand's own oscillation, so the precision loss and the fatigue curve reinforce each other.

Studying it

A typical setup has participants hold their arm unsupported while performing a pointing or tracking task for an extended period, recording how endpoint error changes over time alongside a subjective fatigue scale (e.g., the Borg scale) or forearm EMG tracking fatigue onset. Some studies directly compare completion time and error rate for the same gesture performed with support versus unsupported.

Methodological note: short lab sessions tend to underestimate the real impact — mid-air fatigue often only becomes apparent after tens of seconds to a few minutes, so a task that is too brief will mostly capture the effect of being unsupported on control itself, missing the compounding degradation once fatigue sets in.

Where it stops holding

This holds for unsupported operations that must be sustained for some duration and that demand a degree of precision; a single, large-amplitude sweep that doesn't need a precise landing point (a coarse swipe to the next page) is much less affected by being unsupported. The fatigue consequence also depends on the height at which the motion occurs — the higher the arm is raised, particularly at or above shoulder level, the greater the load and the sooner fatigue appears.

Applying it

• Do not design interactions requiring sustained or repeated fine pointing to be performed unsupported, especially not with the arm held above shoulder height for extended periods.
• For in-air gestures and large-display interaction, place fine-selection actions at a height close to the body where the arm can hang naturally or find some support, and reserve large unsupported motions for coarse operations (page turns, zoom) that don't require a precise landing point.
• To verify: have users perform the same unsupported task continuously for several minutes, recording endpoint error and subjective fatigue rating minute by minute — a clearly rising error curve indicates the interaction is unsuitable for sustained mid-air use.

Related

• Same group: A8.14.1 Wrist or pinky support markedly improves pointing precision · A8.14.3 A support surface constrains the available range of motion · A8.14.4 Mobile contexts usually lack a stable support surface
• Nearby: A8.19 Fatigue from sustained arm elevation · A8.20 Static versus dynamic load · A8.15 Physiological tremor
• Search terms: mid-air interaction · gorilla arm · unsupported pointing · arm fatigue