Choose the interaction before the device
A large touchscreen is a strong candidate when one interaction should be visible to a group: a guided product demonstration, a shared map or a game with spectators. Tablets are a strong candidate when visitors need separate sessions, private input or a device that a member of staff can carry between conversations. A combination may serve both goals.
Begin with one sentence describing the visitor's task. “Compare two products and ask for a meeting” is more useful than “we need something interactive”. It gives the designer a clear beginning, decision and next step, and makes it possible to compare hardware without confusing screen size with the quality of the experience.
Compare the actual use cases
| Task | Large touchscreen | Tablet |
|---|---|---|
| Staff-led demonstration | Helps nearby people follow the same presentation | Supports a closer conversation or a mobile salesperson |
| Registration or contact form | Needs careful positioning so entries are not displayed to a crowd | Offers separate input positions; still needs privacy and session reset |
| Product catalogue | Works well when products are discussed together | Lets several people browse independently if enough stations are supplied |
| Game | Can make the action visible to spectators | Can distribute short individual games around the stand |
| Wayfinding | Can form a visible destination with a permanent position | Can support an information desk or staff assistance |
Do not treat a multi-touch specification as the number of visitors a station can serve independently. Several recognised finger contacts may support one person's gestures or a shared game. Independent simultaneous sessions require an interface and application designed for that arrangement.
Check the application before confirming hardware
A touchscreen may use an integrated computer or connect to a separate one. A tablet runs within its own operating system and application environment. Provide the supplier with the working application, supported platforms and any peripherals before confirming the device. A screenshot proves neither compatibility nor reliable touch behaviour.
Test the complete path: launch, language choice, navigation, keyboard entry, video, submission, confirmation and return to the start. Include the real content volume. A demonstration with three products may conceal awkward navigation in the final catalogue of sixty.
On iPad, Apple provides Guided Access to temporarily restrict the device to one app and control selected functions. Treat that as one configuration option, not a complete unattended-event plan. Someone must still know how to recover the session, manage charging and help a visitor who gets stuck.
Worked example: independent sessions and queue capacity
Assume a hypothetical product selector takes three minutes to complete, followed by one minute for questions, clearing the previous session and preparing the next visitor. One station then has a mathematical ceiling of 60 divided by 4: fifteen sessions per hour. Four independent stations have a combined ceiling of sixty.
Those figures are not a throughput forecast. Visitors arrive unevenly, some need more explanation, and interruptions consume time. Measure several trial sessions and include handover time before deciding the station count. A single large touchscreen still provides only one session at a time if its application follows that workflow, however many touch points the hardware supports.
For this imagined stand, compare two designs: four tablet stations for self-guided selection, or a large touchscreen for shared demonstrations plus two tablets for individual follow-up. Choose between them according to the goal: completed selections, conversations with sales staff or an audience watching a presentation. The highest theoretical session count is not automatically the most useful result.
Design the physical experience as well as the interface
Try the proposed screen position with people standing and sitting. Check reach to the top and bottom, reflections, space in front and where a waiting visitor would stand. A larger interface can become harder to operate if its controls are spread beyond comfortable reach.
The W3C guidance on pointer targets explains why controls need adequate size or spacing. Its CSS-pixel criterion is not a physical sizing rule for an event installation. Test the actual display and interaction, including an alternative way to receive assistance.
Keep public demonstration content separate from personal entry where practical. Decide when a session clears, what confirmation visitors see and who handles incomplete submissions. Ask which functions still work if connectivity disappears; a web application should not be assumed to work offline simply because it opens in a browser.
What belongs in the quote and rehearsal
Confirmed display or tablet, computer if required, stand or enclosure, power and connection accessories.
Application preparation, language versions, content loading and any required licences.
Network assumptions, session reset, recovery procedure and a tested opening sequence.
Staff responsibilities, charging arrangements, visitor assistance and any agreed spare device.
A trial using the final application and representative visitors before approval.
Common mistakes include renting hardware before checking the software, budgeting only for the screen, leaving private data visible to the next user and planning capacity without reset time. Reusing office tablets also needs a review of device configuration and responsibility for returning them to ordinary use.
Send the visitor task, expected peak demand, floor plan and application reference with your touchscreen rental enquiry. For a new experience, discuss interactive installation design or event applications. Tablet models and availability should be confirmed for the particular project.