Interactive apps
Installations built to run a show day unattended
Touch tables, object recognition and sensor-driven screens, built for a full show day of public use and designed to restart themselves.
It worked in the demo, not on the stand
Interactive builds are often signed off in a studio and then left to face the public. By day two the tracking has drifted or an update has broken the camera, and someone from your team restarts it between visitors. Nobody specified what the screen shows while that happens, so it shows a desktop.
Designed from the failure states back
01
Interaction mapped to the room
We map the physical setup first: where people stand, how many use it at once, and what a sensor sees under stand lighting. The interaction is then written to fit the room, not the other way round.
02
Build against the real hardware
Touch, object recognition and sensor work is developed on the same machines, cameras and screens that will ship. Calibration is a documented step, not a setting one person remembers.
03
Recovery states before polish
Attract loops, timeouts when a visitor walks away, watchdog restarts and an offline mode are specified early and tested. If something drops, the screen moves to a designed state instead of an error window.
What arrives on site
01
The application installed on the machine, screen, camera or sensor it ships with, calibrated in place on your stand.
02
A one-page operating sheet for stand staff: how to start it, how to restart it, what each recovery state means.
03
A rehearsal run before doors open with the snag list closed, plus the content, assets and source files at handover.
Work that has already stood up in public
We have built an object recognition table: visitors place objects on the surface and the content responds to what it sees. Event and stand work includes TABADUL at Gitex, BYD, Al Futtaim, Hyundai via Touchpoint, TeamNL Volkswagen via Holy Cow, and Lean.
Tell us the stand, the dates and the idea
Send the floor plan and what you want visitors to do, and we will come back with an approach and a hardware list.