Contact

Planning a kiosk project: hardware and software decisions to resolve in advance

A river lock with barges, houses and tall poplars on the far bank under a cloudy sky. (Camille Pissarro, The Lock at Pontoise, 1872)
Camille Pissarro: The Lock at Pontoise, 1872 · The Cleveland Museum of Art · Public domain
Category
Kiosk · Embedded
Published
Reading time
~3 min read
Author

Summary

A kiosk is a computer working unattended in a public space. Its success depends on designing hardware, software, and day-to-day operations together.

How a kiosk differs from a website

A kiosk, whether a ticket machine, self-checkout, access terminal, or wayfinding screen, is used by people who are in a hurry, seeing the interface for the first time, and have nobody standing next to them to help. Meanwhile, the machine runs all day, often in fluctuating temperatures and on unstable network connections, with no one around to reboot it if it freezes.

That is why the primary requirement for kiosk software is not feature richness, but self-recovery and an interface that is immediately obvious at first glance.

Hardware decisions

Key hardware decision points for a kiosk project
ComponentWhat to decideWhat it depends on
Enclosure & placementIndoor or outdoor; freestanding, wall-mounted, or countertopEnvironment, foot traffic, and vandalism risk
DisplayScreen size, brightness, and touch technologyDirect sunlight, gloved operation, and viewing distance
PaymentCard terminal, cash handling, or noneBusiness model and payment processor certification rules
PeripheralsPrinter, barcode/QR scanner, RFID/card reader, cameraSteps in the user journey: every peripheral adds a potential point of failure
ConnectivityWired Ethernet, Wi-Fi, or cellular with automatic failoverSite infrastructure and reliability requirements
AccessibilityReach height, wheelchair access, and screen contrastTarget audience and legal accessibility standards

Involve your software developers before locking in hardware choices: not every peripheral ships with reliable drivers for your target operating system, and discovering that late is an expensive surprise.

Software decisions

  • Locked-down kiosk mode: users cannot exit the application or reach the underlying operating system.
  • Self-healing startup: after a crash or power outage, the unit reboots and returns to the home screen without human intervention.
  • Offline behaviour: decide what the kiosk can still do when the network drops, and how locally queued data is synced later.
  • Session timeout: after inactivity, the screen resets and wipes any data entered by the previous user.
  • Peripheral fault handling: define what happens when paper runs out or the card reader stops responding.
  • Multilingual, high-clarity UI: large tap targets, minimal text, and an unmistakable next step on every screen.

Operations: the invisible half of the project

You can babysit a single kiosk in person. Once you deploy ten or a hundred units across multiple locations, operating them without remote management quickly becomes untenable.

  1. Remote monitoring: a dashboard showing which units are online, which are low on paper, and which have missed heartbeats.
  2. Over-the-air updates: rolling out software updates in stages without site visits, with automatic rollback if an update fails.
  3. Central content management: updating prices, copy, and media from one place.
  4. Diagnostic logging: detailed logs so intermittent faults can be investigated after the fact.
  5. Field service: clear SLAs on who goes on site, how quickly, and what spare parts are kept in stock.

Start with a real-world pilot

Kiosks are a medium where reality always brings surprises: glare on the screen, patchy cellular signal, or the way people actually tap and swipe. Before rolling out a full fleet, run a pilot with one or two units at an actual location and watch real users interact with them.

Do not overlook physical and network security either: because a kiosk sits in a public space, exposed ports, the boot sequence, local storage, and network traffic must all be locked down. For payment kiosks, card-scheme security standards set strict mandatory requirements.

Key takeaways

  • A kiosk operates unattended; its most important capability is recovering automatically from faults.
  • Design hardware and software together; every added peripheral introduces another point of failure.
  • Decide up front how the kiosk behaves when network connectivity drops.
  • Without remote monitoring and over-the-air updates, a multi-unit fleet cannot be operated economically.
  • Always run an on-site pilot with real users before committing to a full fleet rollout.

Frequently Asked Questions

Can we build a kiosk out of a commercial tablet?

For simple indoor tasks (such as visitor check-in or product information), a commercial tablet in a secure enclosure running in kiosk mode can work well. For continuous heavy traffic, outdoor placement, or multiple hardware peripherals, purpose-built industrial hardware is far more reliable.

Can kiosk software be built with web technologies?

Yes, and in many cases that is a practical choice because UI and content updates are straightforward. However, talking to hardware peripherals and enforcing a locked-down kiosk mode typically requires a native wrapper around the web interface.

What drives the cost of a kiosk project?

The number and grade of enclosures, attached peripherals, payment integration, backend system connections, and the required service-level agreement for fleet operations and field maintenance. Always budget for total cost of ownership over the fleet's lifespan, not just initial hardware and software.

Facing a similar decision? We are happy to talk it through.

Let's talk