Kiosk Mode
Kiosk mode: configuring a device (tablet, kiosk, screen) locked to a single full-screen app, with no access to the rest of the system, for a dedicated use.

Kiosk mode refers to configuring a device, whether a tablet, a kiosk, a wall screen or a TV, so it is locked to a single app displayed full screen, with no access to the rest of the system. The term comes from interactive kiosks in public places; today it applies just as well to a store checkout as to the wall-mounted tablet that runs a home. The stakes for an organization are twofold: deliver a frictionless experience to the user and keep control of a device nobody is watching.
Technical definition
Three levels of lockdown
A kiosk browser is an ordinary app that displays a web page full screen, hides its own interface and protects it behind a gesture or a password. It is the most common solution for home dashboards. A dedicated home app goes further: set as the default launcher, it opens at startup and replaces the home screen. Android's lock task mode, available since version 5.0, is the strictest level: a device management app enforces the app, blocks notifications and disables the system buttons.
What the app has to handle itself
A dedicated screen runs with nobody in front of it most of the time. The app it displays must therefore be able to update itself, dim the screen after a period of inactivity, wake up on the first touch, and detect that the screen has turned off and back on. Kiosk browsers often expose these functions to the web page, brightness included, which saves installing anything else.
The details that make the difference
The display density declared by Android determines the size the web page thinks it has: a 1920 × 1080 screen declared at 240 dots per inch behaves like a 1280 × 720 screen. The server's certificate must be trusted by the web view, which takes an extra step when you use a local certificate authority. And the power source matters: a tablet that is always plugged in ages better with adapted brightness and sleep cycles.
Current challenges
Dedicated screens come back through the home
After kiosks and checkouts, kiosk mode is entering homes through home automation: a tablet in the kitchen, a small screen in the entryway, a TV showing the state of the house. Home Assistant and kiosk browsers have made it common practice, and devices designed for something else, digital photo frames first among them, are repurposed as low-cost screens. I wrote about repurposing a Frameo frame, following Wes Bos's work.
The PWA as natural content
The pairing of PWA and kiosk mode has become the go-to combination for dedicated screens: the app lives on a server, the screen loads it and updates without intervention, and the kiosk simply displays it and manages the device. All business logic stays server-side, which simplifies security and operations.
A security blind spot
A device in kiosk mode is often forgotten: it shows the right page, so everything must be fine. Yet it is still a networked computer, sometimes with a camera and microphone, and cheap models ship with network debugging access left open. Kiosk mode protects the use, not the device; it must be part of a defense in depth strategy: a separate network, debugging access closed, updates, and an inventory of what is plugged in.
Standards and Specifications
Android lock task mode
Native Android mechanism (since version 5.0) that runs an app in an immersive, kiosk-like mode under the control of a device management app
Frequently Asked Questions
What is the difference between kiosk mode and screen pinning?
Screen pinning is a consumer setting: it locks the device to one app, but the user can leave it with a button combination or a PIN. Kiosk mode in the strict sense, called lock task mode on Android, is enforced by a device management app: the user can neither leave the app, nor reach the settings, nor see notifications.
In between, kiosk browsers such as Fully Kiosk Browser offer a middle ground: full screen, a menu hidden behind a gesture or a password, brightness and sleep settings, without fleet management.
How do you exit kiosk mode?
It depends on how it was set up. A kiosk browser provides a hidden gesture (for example, holding two fingers on the screen) or a password. A device managed in lock task mode is released from the management console or by removing the management app. On a device where you have debugging access, a single ADB command is enough to restore another home app.
The design rule: decide from the start who must be able to get out, and document the procedure, because a locked screen nobody knows how to exit ends up unplugged.
What hardware should you use for a home automation screen in kiosk mode?
Any entry-level Android tablet will do to display a web app, as long as you tune brightness, sleep and updates. Unexpected devices also work: a digital Android photo frame can be taken over and turned into a wall screen, as I did for my entryway with the kiosk from Wes Bos's photo-frame-dashboard project.
Two technical points matter more than raw power: the display density declared by Android, which determines the actual size the page sees, and screen-off handling, which the app must be able to detect in order to wake up.
Is kiosk mode a security measure?
Partly. It prevents misuse of the screen, not an attack on the device. A tablet in kiosk mode is still a networked computer, sometimes with a camera and a microphone, and cheap models often ship with debugging access left open from the factory.
So treat it like any other connected device: a segmented network, updates, debugging access closed or controlled, and an app served over HTTPS with a strict Content Security Policy.