What is kiosk software?

Leave a computer in a public space and somebody will eventually try to find out what else it does. Not usually maliciously. People poke at things.

Kiosk software is the layer that decides what they find. It restricts a machine to an approved task, hides everything underneath and puts it back the way it was for the next person.

What it actually restricts

At minimum, working kiosk software does five things.

Launches one thing. An application or a web page, full screen, with no visible way out.

Hides the system. No desktop, no taskbar, no file manager, no settings.

Blocks the escapes. Keyboard shortcuts that reach the task manager or the desktop, right-click menus, file dialogs, print dialogs that open a browser, removable storage.

Prevents changes. No installing, no configuring, nothing that survives the session.

Recovers on its own. If the locked application crashes or somebody closes it, the machine reopens it rather than sitting on a bare desktop until staff notice.

That last point is the one people skip and it is the one that produces the photograph of a broken self-service terminal showing an error dialog in a shopping centre.

The built-in options

You do not always need a product. For simple cases the platform may be enough.

Windows includes assigned access, which limits a sign-in to a single application. Microsoft documents the approaches to configuring a Windows kiosk directly. Browsers have their own kiosk switches that open full screen with the interface stripped away.

These cover a single terminal doing one job. What they do not cover is a fleet: managing many devices centrally, seeing whether each one is alive, pushing a change to all of them and dealing with the machine that quietly dropped off the network last Tuesday. That gap is the reason dedicated products exist and it is the subject of kiosk management.

Single-purpose is not the only shape

Here is the distinction that trips people up when they go shopping.

A single-purpose kiosk shows one thing: a check-in screen, a ticket machine, an ordering terminal, a museum display. Full lockdown is exactly right, because anything the user reaches beyond the app is a failure.

A shared general-purpose computer is different. A library terminal, a school lab machine, a hotel business centre, an internet cafe PC. The user is supposed to browse, type a document, print, play something. You cannot lock it to one application, because being useful is the point.

That second case needs a different combination: broad restriction rather than a single locked app, plus session control, plus a reset that clears the last person completely. It is closer to PC management for shared machines than to a ticket terminal, even though both live under the kiosk heading.

The reset is the real feature

Lockdown gets the attention. The state between users decides whether the machine is actually safe to offer.

Accounts left signed in. Downloads in a folder. A browser full of somebody's history. A saved password. Files on the desktop. Each of those is a privacy problem for the person who left and a nuisance for the person who arrives.

A public machine should return to an identical starting state every time, without staff doing anything. If that reset depends on somebody remembering, it will not happen on a busy afternoon, which is precisely when the machine turns over fastest.

Choosing the right depth

The question to answer before buying anything: does this device do one thing or does it need to stay generally useful?

One thing, small number of devices, on Windows: the built-in assigned access may be all you need. One thing, many devices, spread across sites: you want a managed product with monitoring and central updates.

Generally useful machines with unknown users: you need restriction, session control and reset together, which is a different category with a different shape. Buying a single-app kiosk tool for a room of public computers is the mistake that leads to somebody disabling most of it within a month so the machines can do their job.