On shared displays the contact cap bounds concurrent participants

What it is

On a shared large display—a meeting whiteboard, a museum kiosk, a checkout island—the contact budget first limits how many people can act at once, and only secondarily how many fingers one person may use. A board rated for ten contacts, if each pinch costs two fingers, theoretically holds five people; a palm, a sleeve, or two-handed work drops that number immediately. Headcount is not an operations parameter. It is input capacity divided by slots consumed per person.

Why it happens

A large panel maps several people’s hands onto one slot table. The system rarely partitions by person; it queues blobs. Two people dragging at opposite ends are the same load to the controller as one person with ten fingers down. Inter-person spacing is usually larger than a single user’s two-finger span, so merging is not the main limit—slot count is. Task profiles differ sharply: a pointing bystander costs one slot, a zoom costs two, a two-handed marquee costs four. A design that assumes “every visitor can pinch” halves the people cap by construction. In a classroom, the teacher’s system gestures (three-finger clear, edge back) tax the table further, and students lose fingers first.

Studying it

On the real target size—or an engineering unit with the same controller—recruit 2–8 people to act at once (each dragging their own card, pinching together, one writing while another scrolls). Independent variables are headcount, fingers per person, stance (opposite sides versus same side), and whether system gestures are on. Dependent measures are how many people succeed concurrently, silently dropped actions, completion time, and spoken “I tapped and nothing happened” reports. Do not simulate two people with one person in two gloves: slot contention matches, social stance, mutual occlusion, and blame attribution do not. Report mean slots consumed per person; that figure is more useful than the device’s headline cap.

Where it stops holding

If hardware or software zones the panel (independent controllers per half), the people cap becomes the sum of per-zone caps and whole-panel division no longer applies. Optical and infrared frames often hit ghosting from extra bodies and reflections before the slot table fills; sensing noise is then the limit. Children’s smaller contacts and closer stance can merge before slots run out. A “one person at a time” guided tour does not consume this constraint; only genuine parallel action makes headcount a function of the contact budget.

Applying it

• Fix slots-per-person by task, divide the measured device cap by that number, and publish the promised concurrency in the exhibit copy or the lesson plan.
• Replace high-slot actions (two-handed zoom, multi-finger rotate) with one finger plus an on-screen button, spending slots on more people dragging at once.
• Accept with real headcount rather than a developer’s two hands: run the target stances together, count non-responses, and cut concurrency or add zoning if the count is high.

Related

• Same group: C2.18.1 Hardware and the OS cap how many contacts can be tracked at once · C2.18.2 Overflow contacts are dropped silently rather than signaled as errors · C2.18.4 Contact limits vary by device generation and cannot be assumed uniform
• Nearby: C4.17 Input attribution and multi-user arbitration · C4.30 Bystanders and third parties
• Search terms: multi-user touch · contact budget · shared display