Knowledge base

Interactive touch table: requirements, prototype and use tests

Plan an interactive table around users, reach, touch behaviour, light, content and recovery. Test ergonomics and maintenance before committing to a finished enclosure.

A horizontal screen does not by itself make a useful interactive table. The application must make sense from the intended viewing positions, handle simultaneous touches and survive the physical environment.

Begin with one task: for which users, in which location, does the table improve which activity? A showroom comparison, museum experience, game and meeting tool have different requirements. More technology does not automatically improve the task.

Define users, positions and the environment

Record whether people sit or stand, use the table together, approach from several sides or need assistance. Consider reach, wheelchair access, height differences, dexterity, gloves and session length.

There is no natural top edge for everyone around a table. Choose a fixed operating position, rotating content or separate user zones. Explain what happens when two users select the same object or change a shared state at the same time.

Test reflection, light, noise, dust, cleaning, moisture, temperature, power and network availability. An office prototype may be unreadable in a bright showroom. Include cable routing and access for maintenance in the location assessment.

Select screen, touch and enclosure together

Screen size follows reading distance and simultaneous information needs. A larger surface also increases reach. Do not place an essential control where intended users cannot comfortably reach it.

Assess viewing angles, brightness, heat, mounting and component availability. A consumer television may support an experiment without establishing suitability for continuous embedded use.

Specify simultaneous touches, required glove or stylus behaviour, accidental palm contact, accuracy and acceptable delay. Test after the screen, protective layer and touch hardware are assembled. A cover can change reflections, response and heat.

Keep the enclosure serviceable

The enclosure needs stability, suitable load support, protected cables, ventilation, accessible components and appropriate edges. Plan a service opening or disassembly route. An attractive sealed tabletop creates a maintenance problem if a small component cannot be replaced without damage.

Design the software for horizontal and shared use

Use clear touch targets, visible feedback and short paths. Avoid essential hover menus or right-click actions. Define concurrent input, accidental swipes, abandoned sessions, network loss and invalid external records.

Assign content ownership. Decide which texts, media or product data change and how staff update them. A flexible CMS adds value only if the required variation and operator are known; a fixed demonstration may need a simpler process.

Reset abandoned and public sessions

Public sessions should reset to a neutral start and remove personal inputs appropriately. Define a warning before timed reset and a route back. Essential information should not depend solely on colour, sound or motion.

Prototype in stages

Prototype in stages
StageUncertainty to test
Interface prototypeCan a user understand the task and sequence?
Ergonomic modelAre reach, height, viewing angles and reflection workable?
Integrated prototypeDo touch, ventilation, cables, restart and sustained use work together?
Location pilotCan real users finish the task without constant explanation?

Observe completion, errors, conflicting touches, requests for help and recovery after interruption. Check whether an operator can update content, inspect the running version and restore the application. Preserve configuration and startup instructions so the setup does not depend on one person.

Decide when to stop or redesign

Reconsider the table if a tablet or ordinary display serves the task more easily, touch fails in the real environment, users constantly need help, reset exposes earlier information or maintenance requires damaging the enclosure.

Mechanical stability, electrical installation, heat, liquid exposure and location requirements need appropriate assessment before unattended public use. A working technical prototype alone is not that evidence.

Write a prototype brief covering users, environment, core task, interaction, content, hardware, enclosure, recovery and the use test that would justify the table over a simpler option.

See the smart table experiment and other OmniTechs Lab projects. The experiment is evidence of exploration; its publication does not establish a finished product or validated public installation.