Kiosk UI/UX Design: Best Practices for Touchscreen Flows, Timeouts, Languages and Error Recovery
By MHY Engineering Team · Updated
A kiosk interface has about thirty seconds to succeed. The user is standing, often in a hurry, sometimes in a queue, with no manual and no one to ask. Unlike a website, there is no back button habit, no login, and no second visit to learn the layout. Good kiosk UI/UX design is therefore less about visual style and more about removing decisions, preventing errors and recovering gracefully when the machine or the user gets stuck. This guide covers the principles that work across ordering, payment, check-in and information kiosks, and how the hardware you choose limits or supports them.
1. Design for the walk-up user
Assume the user has never seen this kiosk, is standing at arm's length, may be carrying a bag or a child, and wants to finish and leave. Three rules follow from that:
- One task per screen. A screen asks one question or shows one result.
- Say what the machine does before the user touches it. The idle screen must answer "What is this and what do I get?"
- Never require training. If a step needs an explanation, rewrite the step.
2. The attract screen
The attract (idle) screen is the kiosk's signboard. It should show the main action in a few words and a large start button such as "Touch to order" or "Touch to pay a bill", in the languages of your area. A looping video can attract attention, but it must stop the moment the screen is touched and must never delay the first response. Show real prices or real products, not stock slogans. If the kiosk also works as a sign, our digital signage displays can carry the same content.
3. Keep the flow short
| Kiosk typeTargetTypical mistake | ||
| Self-order (restaurant) | Order in under 90 seconds | Too many upsell screens before checkout |
| Bill payment | Pay in under 60 seconds | Making users type long account numbers instead of scanning |
| Check-in or ticketing | Under 30 seconds | Asking for data the system already holds |
| Information or wayfinding | Answer in 3 touches | Deep menus copied from a website |
Count the touches from idle screen to receipt, then cut every step that does not change the result. Show progress ("Step 2 of 4") and always show where the user is. For the business view of ordering flows see self-order kiosks for restaurants, and for ticket flows see the queue management kiosk guide.
4. Touch targets, layout and readability
- Target size. Make buttons large and spaced; a common guideline is at least 9 to 10 mm on the glass for any touch target, and larger for primary actions. Fingers, gloves and shaky hands miss small buttons.
- Reach. Put the main actions in the zone between roughly waist and shoulder height; keep the bottom edge free of small targets, especially on tall portrait screens.
- Contrast and text size. Use high-contrast colours and text readable from arm's length; do not rely on colour alone to signal state.
- Feedback in under 100 ms. Highlight the button, play a short sound or vibration if available; a silent screen makes users tap twice.
- Glare. A beautiful interface is useless under reflections; see the display selection guide for brightness and glass.
The touch technology itself matters for gloves, rain and accidental touches; our projected capacitive touchscreen guide explains the options.
5. Timeouts, sessions and privacy
Kiosks are shared devices, so a session must end cleanly:
- Inactivity timeout. Warn after about 20 to 30 seconds ("Still there?") with a visible countdown, then return to the idle screen after 10 more seconds.
- Clear the session. Erase typed names, phone numbers and account numbers on timeout, completion or cancel.
- Do not time out mid-payment without a safe state: money inserted must be returned or credited, never lost.
- Mask sensitive input and do not show full card or ID numbers on screen or on a receipt.
The technical controls behind these rules, including kiosk-mode lockdown, are in the kiosk security guide.
6. Languages and localisation
A language switch is a design feature, not a settings page. Put it on the first screen, use each language's own name ("Español", "العربية", "Русский", "Bahasa Indonesia"), and keep it visible on every screen. Remember:
- Right-to-left languages such as Arabic need a mirrored layout, not just translated text.
- Translated labels can be 30 to 40 percent longer; design buttons that tolerate it.
- Currency, date, number and phone formats follow the locale.
- Use icons with text, not icons alone, and avoid idioms.
The same principle applies to your website: this guide itself is available in several languages on this site.
7. Accessibility is part of the interface
A usable kiosk works for a seated user, a person with low vision and someone who cannot read the language. That means reachable controls, adjustable text size, high-contrast mode, audio guidance through a headphone jack and a tactile keypad where PIN entry is needed, plus a staffed alternative. Read the accessibility guide (ADA and European Accessibility Act) for requirements, and plan these modes from the first wireframe, not as a late add-on.
8. Errors and recovery: where good design shows
Hardware fails, networks drop and users make mistakes. The interface should handle every one without a dead end.
| SituationGood behaviour | |
| Printer out of paper | Warn before the transaction, offer an on-screen or SMS receipt, and alert the operator (see the thermal printer guide) |
| Card or note rejected | Say why in plain words and offer another payment method |
| Network lost | Show a clear message, keep collected money safe, and record the state for recovery |
| Scanner cannot read an ID or code | Offer manual entry and a hint about positioning (see the passport reader guide) |
| User stuck | A visible Help button that calls staff or opens a short guide |
Error messages should state what happened, what the user can do next, and what the machine has already done with their money. Pair this with remote monitoring so the operator knows before the next customer arrives; see the remote management guide.
9. Match the interface to the hardware
- Screen orientation and size. Portrait 21.5 to 32 inch suits menus and wayfinding; smaller screens suit ticketing and payment.
- Peripherals. Put the card reader, scanner and printer where the interface tells the user to look, and use animation to point at the right slot.
- Performance. A lagging interface feels broken; choose a computer that renders animations smoothly, and compare options in Android vs Windows kiosk TCO.
- Enclosure. Screen tilt, hood and slot positions shape usability; see enclosure design and customization.
10. Test with real users before you scale
- Build a clickable prototype and watch five people use it without help; note where they hesitate.
- Run a pilot in one site for three to four weeks, with the real hardware and lighting.
- Measure completion rate, time to complete, abandonment per screen, error rate and Help presses.
- Fix the top three problems and repeat before rolling out to more sites.
11. Interface specification checklist
| ItemDefine | |
| Flow | Steps from idle to receipt, target time, upsell rules |
| Languages | List, default, right-to-left support, switch position |
| Timeouts | Warning time, reset time, safe state during payment |
| Accessibility | Audio, text size, contrast, reach heights, staffed alternative |
| Error handling | Messages, fallbacks, operator alerts |
| Content update | Who edits menus, prices and languages, and how it is deployed |
| Analytics | Which events are logged, retention, privacy |
12. Next step
Tell us the kiosk type, languages, peripherals and venue. MHY engineers can configure the hardware, supply an SDK or standard interface, and support a pilot. Explore our self-service kiosks, check OEM/ODM options, or request a quote. For background, read the complete guide to kiosk types and the RFQ template.
Need help specifying hardware for your project?
Tell us your use case and volume — our engineers will recommend a configuration and quote it.