Service · App development

Custom kiosk app development for self-service in public spaces.

A locked-down kiosk application for self-ordering kiosks, check-in kiosks, ticket machines or information panels. We build the software for Android, iOS or Windows kiosk mode and integrate it with your existing systems, payment terminal, printer and scanner.

Kiosk modeTouch UIPayment terminalRemote management

A kiosk is not an ordinary app.

The user is usually standing in front of the screen for the first time, and sometimes has only thirty seconds. No menus, no manual, no IT helpdesk nearby. The interface has to be understandable at once: for a tourist wearing gloves, for an elderly visitor, for someone who doesn't read Dutch. That forces choices you rarely need to make in an ordinary app: fewer screens, bigger buttons, more icons, shorter text and always a clear way back.

At the same time, the thing must not be able to break. A kiosk app sometimes runs for months without a restart, can't be Alt-Tabbed to a browser, restarts automatically after a crash, and must not freeze when the network goes down. We have been building kiosk apps since 2017 for public spaces, healthcare reception desks and hospitality venues, each time custom-built, with attention to the hardware context the software runs in. The combination of a locked-down operating system, good UX design for standing users and reliable integrations with the payment terminal, printer and scanner makes or breaks the product.

From the first session, we look at the whole chain: where the kiosk stands, who walks past it, which flow it needs to support, which systems sit behind the scenes, and how you keep central control of hundreds of devices in the field. Those questions determine whether a lightweight web kiosk will do or whether you need a fully native production application.

Three types of kiosk app.

It depends on where the kiosk is placed, who operates it and how deep the integration with your back office needs to be. In the first conversation we advise which one fits: sometimes a lightweight web kiosk is enough, sometimes a proper native app is needed.

Compact project · fixed sprint budget

Web kiosk in browser mode

A progressive web app that runs in full-screen mode on a tablet or touchscreen. Suitable for information kiosks, audio tour information in museums, production feedback in factories or visitor surveys. Quick to roll out across a large fleet, easy to update without an app store process, and easy to connect to your existing web environment or CMS. A good choice if you are still learning how users interact with the kiosk and flexibility matters more than deep hardware integration.

PWABrowser lockdownTouch UIAuto-refresh
Mid-sized project · fixed sprint budget

Native self-ordering or check-in kiosk

An Android or iOS application running in true kiosk mode on an Elo, Touchsystems, Panasonic or similar touchscreen. For self-ordering kiosks in retail and hospitality, check-in kiosks in hospitals and outpatient clinics, or ticket sales in museums and leisure venues. Deep integration with your point of sale, scheduling or patient system and the receipt printer. Works offline when the network falters, syncs automatically later and runs stably even if the screen never switches off.

Android kioskiOS kioskReceipt printerMulti-language
Larger project · fixed sprint budget

Production kiosk with payment and hardware stack

Mission-critical kiosk application with payment terminal, scanner, camera and printer integration. For self-order kiosks with instant card payment, ID-scan kiosks at government agencies and banks, or parking and transport machines. Full telemetry and remote management for your rollout, plus SLA monitoring so you know which kiosks are offline.

Adyen/Worldline/CCVBarcode & QR scanningID scanningTelemetry & SLA

What you get at the end.

A production-ready kiosk application, including everything you need to put it into production and manage it yourself.

  • The kiosk application itselfNative Android or iOS build (APK/IPA), Windows kiosk-mode installer or web kiosk PWA. Delivered in production and staging versions.
  • Locked-down configurationKiosk-mode policy so users can't leave the app, automatic restart after a crash, and disabled notification bar and hardware buttons.
  • Hardware integrationsWorking integration with your receipt printer (ESC/POS), badge printer, barcode scanner, ID scanner, camera and payment terminal from Adyen, Worldline or CCV.
  • Remote management dashboardA central console where you see all your kiosks at a glance: uptime, sessions per day, error rates, and the ability to roll out updates or restart a kiosk remotely.
  • Codebase and documentationFull source code, build instructions and an architecture overview. Plus a runbook for your IT team covering support and incident response.
  • Maintenance contract (optional)Monitoring, security patches, OS upgrades and ongoing development. Fixed monthly price with response-time tiers depending on how critical your kiosk fleet is.

Modules we build regularly.

Not every kiosk needs everything. We split the project into modules so you choose what fits the flow at your location. This is what we deliver most often.

Kiosk mode and auto-recovery

Locked-down operating system, no escape to the underlying OS, no access to notifications or system settings. Automatic restart after a crash, and a watchdog that detects hangs and restarts the app without anyone having to visit the site.

Touch UI for standing users

Large tap targets, high contrast, simple screen flows, and glove-friendly for factories or colder environments. WCAG 2.1 level AA where the sector requires it, with optional text-to-speech for accessibility.

Camera and scanner integration

Barcode and QR scanning for tickets, boarding passes and products. ID scanning via NFC or OCR for passports and driving licences at government and bank kiosks. Camera input for age or identity verification where this can be done in a GDPR-compliant way.

Printer integration

Receipt printer via the ESC/POS protocol for till receipts and waiting-room queue numbers. Badge printer for visitor passes and patient stickers. Connection via USB, Bluetooth or network, with retry and error handling when the paper runs out.

Payment terminal integration

Unattended payment terminals from Adyen, Worldline, CCV and similar providers. Contactless card payments, iDEAL via QR, Apple Pay and Google Pay where needed. A fully PCI DSS-compliant flow without you ever handling card data.

Sound and text-to-speech

Audio feedback for buttons and confirmations, plus full text-to-speech for visually impaired users. Important for government and transport kiosks, where WCAG compliance is often a tender requirement.

Telemetry and SLA dashboard

A central console where you see all your kiosks at a glance: uptime, sessions per day, error messages and hardware status. Alerts to your service team when a kiosk goes offline or a specific component (printer, scanner, terminal) fails.

Auto-updates without a site visit

Over-the-air updates of the application and underlying OS components via an MDM such as Scalefusion, Hexnode or your own channel. First to a pilot kiosk, then in phases. No engineers needed to roll out a new version.

Multi-language and localisation

Multiple languages on a single screen, with automatic detection or a flag selector. For tourist locations, Dutch, English, German and French as standard, with Spanish, Italian and Chinese as options. Date, time and currency formats per locale.

Offline mode and network failover

The kiosk keeps working when the wifi drops. Orders, check-ins or tickets are stored locally and sync as soon as the network is back. For mission-critical locations, we build in 4G/5G failover as a second path alongside wifi.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Who we build kiosk apps for.

The applications vary enormously, from a McDonald's-style self-ordering kiosk to a check-in kiosk at an outpatient clinic. Here are four sectors we work in more often.

Retail & hospitality

Self-ordering kiosks

Customers order and pay themselves, with no staff in between. Works for fast-casual restaurants, food courts, sandwich shops and petrol station shops. Receipt from the printer, order number on the screen in the kitchen. Integration with your existing till or POS.

Healthcare

Check-in kiosks

Patients check in themselves at a hospital or outpatient clinic. Identification via DigiD, date of birth or patient number, integration with HiX, ChipSoft or Epic, and a badge printer for waiting room routing. Set up with care for GDPR compliance.

Government & transport

Ticket and application kiosks

Passport and ID application kiosks at municipal service desks, parking tickets, NS and Connexxion locations, and museums and theme parks. Mostly in public spaces: robust, vandal-resistant, and available without staff.

Industry & banking

HR and cash kiosks

Check-in and feedback kiosks in factories for shift registration and production reports. Unmanned cash and coin deposit kiosks at banks. Operable with gloves on, and clearly legible under factory lighting.

How a kiosk project works.

1

Introduction and hardware selection

A conversation in which we learn who will use the kiosk, which flows it needs to support, and which hardware is already in place or still to be chosen. We build the software; for the enclosure and the touchscreen, we work with suppliers such as Elo, Touchsystems and Panasonic, or a custom builder if you prefer. Read more about our app development in the broader sense.

2

Planning, screen flow and user testing

A workshop with your team plus a test with real end users: a handful of people clicking through a prototype themselves. At the end: a concrete scope, the screen flow, and a first UI in Figma. This is where we learn which texts are too long, which icons are unclear, and which buttons are too small for gloves.

3

Building in sprints

A working build on your target hardware every two weeks. You test along, and so do your end users where possible. We integrate with the printer, scanner and payment terminal early on, because that is where hardware reality always turns out to differ from the documentation.

4

Rollout and remote management

A first pilot location, then a phased rollout across your entire fleet. From the remote management dashboard you can see which kiosks are on, which sessions they have handled and where errors occur. We roll out updates centrally, with no one needing to be physically present.

Frequently asked questions.

What clients usually want to know before we start a kiosk project.

Do you also supply the kiosk enclosure and hardware?
We build the software. The enclosure and touchscreen come from specialist suppliers: Elo, Touchsystems, Panasonic Touch and custom builders such as Almex or HitachiPay. We do help with hardware selection and make sure the software runs on the type of kiosk you choose. For software vendors who want to connect their kiosk enclosure to our application, we can also provide drivers and SDK integrations.
Native app or web kiosk: what is the difference?
A web kiosk runs as a browser in full-screen mode on a tablet or PC: quicker to build, easier to update, and no app-store process. A native kiosk app has access to hardware (printer, scanner, payment terminal), can run in a true locked-down kiosk mode, and works offline. For information and survey kiosks a web kiosk is usually enough; for self-ordering or check-in with hardware, native is almost always the right choice.
How exactly does locked-down kiosk mode work?
On Android, through a COSU or single-app kiosk policy (formerly COSU, now Android Enterprise). On iOS, through Guided Access or an MDM profile. On Windows, through Assigned Access. Users cannot leave the app, see no notification bar, hardware buttons are disabled, and after a crash the system automatically restarts the same app. We configure this, plus an MDM so you can manage devices centrally.
Which payment terminals can you integrate?
Adyen, Worldline, CCV, Buckaroo and similar providers with an SDK for unattended terminals. For online payments (iDEAL, Apple Pay, contactless via QR) we integrate Mollie, Stripe or MultiSafepay. Which combination works best depends on your existing contracts and the type of kiosk, and we will advise you on that. See also our smart API integrations for how we build the integration with your back office.
How do you handle accessibility and WCAG?
Large tap targets, high contrast, screen-reader support where possible, and text-to-speech for visually impaired users. For public kiosks (government, transport, healthcare), WCAG 2.1 level AA is often mandatory, and we work towards it as standard. Multi-language support is usually part of the scope too, with automatic detection or a flag selection on the start screen.
Can we update and monitor kiosks remotely?
Yes. For a kiosk fleet this is effectively a requirement, as visiting each one physically for an update doesn't scale. We deliver a dashboard showing all your kiosks: uptime, sessions per day, error rates and battery status. We roll out updates centrally, first to a single pilot kiosk, then in phases to the rest. If a kiosk goes offline, your team gets an alert automatically.
What determines the cost of a kiosk app?
Mainly the number of hardware integrations (printer, scanner, payment terminal, camera), the complexity of the back-office integration, the number of languages and the number of flows. A lightweight single-screen web kiosk is a different project from a production kiosk with payment, ID scanning and a link to your point-of-sale system. In our first conversation we give you a direction; after the planning sprint you get a concrete scope.
How long until the first kiosk goes live?
A first pilot kiosk can be up and running on location within a few sprints. A production kiosk with payment, hardware integrations and remote management takes several sprints. We always work towards an early pilot at a single location so you can see in practice what still needs doing, because real-world use of kiosks is always rougher than in a Figma prototype.

Talk to us about your kiosk app.

A no-obligation introductory call of half an hour. Tell us where the kiosk will be placed, who will use it, and which hardware and back-office systems we need to work with. We listen and give you direction you can actually use. Our app developers also work on related projects such as an ordering app, a field service app and a custom order management system, which often sit in the same flow.

Edit content