Write the visitor action before choosing the sensor
Complete this sentence: “A visitor will use this installation to…” It might end with exploring a product, answering a question, controlling a character or contributing to a shared display. Then describe the simplest visible action that completes the task. This keeps the control method connected to the purpose of the activation.
Movement can make participation visible to an audience. Touch can provide a direct connection between a displayed choice and a response. A phone can give each participant a separate control surface. These are useful possibilities, not automatic benefits: each needs a clear start, understandable feedback and an exit that releases the experience for the next person.
Compare the complete guest journey
| Method | Good question to ask | What must be planned |
|---|---|---|
| Body or gesture tracking | Does movement itself communicate the idea or create the intended play? | Tracked space, visible instructions, spectator separation and alternative participation |
| Shared touchscreen | Can visitors make meaningful choices directly on the display? | Reach, interface size, simultaneous users and clearing the previous session |
| Visitor phone | Does a personal control surface help people participate together or continue later? | Joining steps, supported browsers, connectivity and an option for visitors without a suitable phone |
| Physical button or controller | Would a small number of obvious actions be enough? | Physical placement, feedback, durability and integration with the application |
Do not compare only hardware prices. Include the application, setup, instructions, staffing and the time each guest spends joining. A phone-controlled experience can still need a host; a touchscreen can still need a custom interface.
Include people who cannot use the main gesture
W3C's pointer guidance explains why complex touch gestures can exclude people and discusses simpler alternatives. Its motion guidance similarly addresses alternatives to motion-triggered functions. Read the pointer explanation and motion explanation. These are useful design references; a complete installation still needs its own accessibility review.
Ask what someone can do if they cannot stand, raise an arm, see a small instruction or hold a phone steadily. An alternative should preserve a meaningful part of the experience. A host pressing every button for a guest may not deliver the same independence as a thoughtfully designed secondary input.
Worked example: choosing a product configuration
Imagine a hypothetical exhibition where visitors choose two product features and see the combination on a shared screen. The brand initially suggests full-body gestures. The available stand space is narrow, and the main objective is a short, clear product conversation.
Compare three prototypes. Touch offers visible feature buttons beside the resulting product. Movement makes the choice a public performance but needs an understandable mapping between gesture and option. Phone control lets visitors make individual selections, but adds a joining step before they see the result.
Ask first-time testers to choose a named combination without explaining the controls in advance. Observe where they pause, what they think has been selected and whether staff must intervene. Check the approach, the selection itself and the reset. Choose the option that supports the agreed objective and physical layout, rather than the one that produced the most impressive demonstration by its developer.
Decide how many people control what
A large display does not imply many independent participants. State whether one person plays while others watch, several people cooperate, or each visitor has an individual session. Identify how the application chooses the active participant and handles an extra person entering or touching the system.
For phone control, test the complete joining route under the intended network arrangement. For touch, test accidental and simultaneous input. For tracking, test someone crossing the edge of the play area. These are different acceptance cases and should appear in the proposal.
Prepare a selection brief
Describe the visitor task and what a successful completion looks like.
State the audience, languages and participation needs.
Provide the usable floor plan and expected simultaneous players.
Agree joining, instruction, feedback, finish and reset behaviour.
Request a prototype test with unfamiliar users and the intended hardware.
Discuss the options through interactive installation design. Include body tracking or event apps when those control methods serve the guest journey. The decision should be demonstrable in a short test.