N5.11.3social awkwardness of mid-air gesturesdesignresearch

Large gestures in public cause social embarrassment and suppress use

Aliases: gesture social acceptability · air gestures · public performance of input · gorilla-arm in public

What it is

Sweep a large arc through empty air to “close a window” in a train car, and bystanders see a performance without an object. Social awkwardness of mid-air gestures makes wearers shrink the motion, or drop the function. Suppression happens before the motion is understood: even if nobody knows what they are doing, the amplitude is already rude.

This is not collision risk, and not unintelligibility. It is the wearer refusing to perform in front of other people.

Why it happens

Public space has an unwritten amplitude budget: touching a phone or adjusting glasses is inside it; a sweep, grabbing air, tapping the void is over. Over-budget is read as odd, aggressive, or filming someone. Wearers rehearse that gaze and delete over-budget moves from the option set. In a lab everyone is doing strange moves, the rehearsal is off, and acceptance inflates.

Small, body-close motions (a fingertip pinch, a tap at the chest) spend little budget because they look like fixing a sleeve or checking a watch. Once an operation sends the hand off the torso and into other people’s visual centre, embarrassment binds to the function: the function is a public performance. People switch to voice — another tax in a quiet car — or give up.

Studying it

Rico-and-Brewster-style social acceptability of gestures: the same set demonstrated in a lab, a café, a bus, scored by wearers and bystanders, plus whether wearers switch to a smaller substitute. Field observation is harsher than a scale: will they finish the set in front of real passengers.

Gesture factors: amplitude, distance from the body, resemblance to a known action (watch, hair). Scores: wearer acceptance, bystander acceptance, actual public use rate, switch to a fallback channel.

Friends as bystanders will score loose. Unknown people have to be present.

Where it stops holding

A desk, a rehearsal room, one’s own home: the amplitude budget is wider, and large moves can stay for efficiency. Games and performances already sit in a “being watched” frame; awkwardness turns into show. When mobility, gloves, or occupied hands leave a large move as the only channel, the social tax has to be counted separately, not deleted. A gesture read as insult or a religious sign escalates from awkwardness to conflict, with large regional spread. When the device is already conspicuous, stacking a large move is a double tax; people will doff the device before they change the gesture.

Applying it

  • Default public input to within-an-elbow, body-close motions: pinch, tap, micro-swipe. Keep sweeps and empty-air grabs for private space or a marked work zone.
  • Give every large move an equivalent small move or a voice/gaze channel, and suggest the switch when crowding or other people enter the view.
  • Do not teach the “cool” large demo as the public default. The motion in a tutorial will be taken as the canonical amplitude.
  • How to check: close a window or pick a menu in a real queue or train car. If the wearer switches to a phone, keeps the hand low, or refuses, amplitude already exceeds that setting’s budget. Completing it in an empty meeting room does not pass.

Related

  • Same groupN5.11.1 Without an externally visible recording indicator, bystanders cannot tell if they are being captured · N5.11.2 How conspicuous the device looks directly affects willingness to wear it in public · N5.11.4 Bystander notice and consent have no unified protocol and depend on venue self-regulation · N5.11.5 Private and public places tolerate different behaviour; the same function must be designed per setting
  • NearbyN5.06 Bystanders · N2.13 Physical Safety of Input (Collisions and Bystanders)
  • Search termssocial acceptability of gestures · mid-air gesture · public performance of interaction

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/N5.11.3