16 November 2026

Exhibition games: from a short interaction to a useful result

An exhibition game should explain the product and fit the flow of visitors. Agencies need to plan entry, participation time, result delivery and readiness for the next person alongside the mechanics. These decisions shape the application and its operating requirements.

Illustration of a concert with blue and purple light rings above the stage and spectators holding smartphones.

Choose an action that explains the product

Start with what visitors should understand. A protection system might become a challenge to choose a response to a situation. A product range might become a task to assemble a selection for a specific need. The action should connect to the message through the result, not only through a logo.

Not every brief needs points or rankings. Comparing options or completing a shared task may be more useful. Write the rules and play through a paper prototype before visual design. Ask someone outside the team to explain the goal in their own words. This exposes unclear rules before graphics and equipment integration begin.

Build the complete play cycle

The sequence includes idle, invitation, explanation, action, result and reset states. Define the visible screen and available controls for each. Visitors need to recognise when an attempt starts, what affects the outcome and how it ends. A short demonstration can explain a rule more clearly than lengthy instructions.

Specify replay, inactivity, mistaken input and departure halfway through. When a tablet controls a large display, both interfaces must agree on the round's state. Losing also needs a clear ending: retry, see an explanation or hand over to the next participant.

Plan visitor flow with the agency

A round is only part of the time spent at a station. People approach, learn the controls, play, view the outcome and collect their result. Staff may need to help between sessions. A one-minute game therefore does not mean sixty visitors per hour. Estimate capacity across the complete cycle and rehearse with unfamiliar participants.

Agree waiting positions and sightlines so the queue avoids blocking circulation and adjacent activities. For higher demand, consider independent stations, a spectator screen or a short demonstration for those waiting. Also provide a way to explore the product without playing: participation will not suit every visitor.

Plan how people receive their result

A result might remain on screen, transfer to a phone through a QR code or prompt a conversation with a representative. Each needs a complete path: visitors see what was created, understand how to receive it and have time to act. If processing takes time, explain the wait and provide a clear exit if it fails.

For files, agree storage, availability periods and link behaviour in advance. The next participant must not receive someone else's result. Make contact collection a separate, explained step; participation alone does not establish consent to further communication. Public rankings can use chosen nicknames rather than contact details.

Connect software to venue operations

For Sber's four festival experiences, we developed applications with different cycles: an arcade with a local leaderboard, a tablet-controlled screen game, QR portrait delivery and smile recognition. Kiosk builds and instructions supported operation on site. Each mechanic defined its own software scope.

For a new project, specify local functions, network dependencies and what visitors see if an external service becomes unavailable. Operators need startup, stopping, session reset and readiness checks. Omelchak delivers agreed software development and integration alongside the agency, stand builder and equipment supplier.

Measure the journey, not just launches

Before opening, define the events to evaluate: starting, completing, receiving a result, replaying and moving to a conversation. Separate visitor sessions from operator tests and technical failures. If the aim is enquiries, agree what counts as a qualified contact and who records subsequent interaction.

A long session can indicate interest or difficulty. Replaying may reflect a desire for a better score rather than purchase intent. Compare data with observation and feedback from stand staff. Our article on evaluating multimedia projects explains these limits. A useful report supports a specific decision: simplify a rule, change delivery or redistribute participation points.