A short definition
Kiosk mode is a way of locking a device so that it runs only what the organization allows. The user sees one app, or a simple home screen with a few approved apps, and nothing else. Settings, the notification shade, the app store and the home screen are out of reach. If the device restarts, it comes back to the same app.
The name comes from information kiosks in airports and shops, but today the term covers any single-purpose device: a warehouse scanner, a delivery driver’s handheld, a hotel room tablet, a classroom tablet during an exam, or a tablet that shows a menu at a restaurant table.
Why organizations use kiosk mode
A general-purpose tablet invites general-purpose use. Without restrictions, users open the browser, install games, change the language or turn off Wi-Fi. Each of these turns a working device into a support ticket.
Kiosk mode solves this in several ways:
- Reliability. The device always shows the app it is meant to run.
- Security. Users cannot reach settings, files or other apps, and cannot install anything.
- Less support. Fewer things can go wrong, so fewer devices need attention.
- Lower cost. A locked-down consumer tablet can replace dedicated hardware for many tasks.
- Shared use. One device can serve several users across shifts.
Types of kiosk
Single-app kiosk
The device runs exactly one app, full screen. There is no home screen and no way to switch apps. This is the strictest form and the most common for customer-facing screens and scanners.
Example: a self-service check-in tablet in a hotel lobby that only runs the check-in app.
Multi-app kiosk
The device shows a simplified home screen with a small set of approved apps, such as the business app, a camera app and a calculator. Users can move between them but cannot reach anything else.
Example: a field technician’s tablet with a work order app, a navigation app and a document viewer.
Digital signage
A variation of the single-app kiosk where the device shows content and accepts little or no input: menus, timetables, advertising or safety notices. The focus is on keeping the screen on and the content up to date.
Comparison
| Single-app kiosk | Multi-app kiosk | Digital signage | |
|---|---|---|---|
| Apps visible | One | A few approved apps | One display app |
| User interaction | Within one app | Within approved apps | Little or none |
| Home screen | Hidden | Custom, limited | Hidden |
| Typical use | Self-service, scanners, exams | Field work, shared staff tablets | Menus, timetables, notices |
How kiosk mode works on Android
Android offers two ways to keep a user in one app, and the difference matters.
Screen pinning is a consumer feature. Any user can pin an app and unpin it again with a button combination. It is useful for handing a phone to a child, but it is not a kiosk.
Lock task mode is the enterprise feature. Only the app that manages the device, the MDM agent acting as Device Owner, can decide which apps may run in lock task mode. Once the device is in lock task mode, the user cannot leave it. The MDM can also choose what remains visible, such as the status bar for battery and clock, or system notifications. This is part of the dedicated device mode of Android Enterprise.
Around lock task mode, an MDM usually adds:
- a custom home screen (launcher) for multi-app kiosks,
- restrictions on settings, factory reset, USB and app installation,
- automatic start of the kiosk app after a restart,
- keeping the screen on while the device is charging,
- silent app updates,
- remote exit from kiosk mode for maintenance.
Because the MDM must be Device Owner, kiosk devices are enrolled as company-owned dedicated devices (COSU). A personal phone with a work profile cannot be turned into a kiosk.
Where kiosk mode is used
| Industry | Example |
|---|---|
| Retail | Price checkers, product catalogs, endless aisle tablets, staff handhelds |
| Education | Classroom tablets locked to the exam app during tests |
| Transport and logistics | Delivery handhelds, ticket validators, vehicle tablets |
| Hospitality | Room tablets for guest services, reception check-in |
| Healthcare | Patient information screens, shared ward tablets |
| Mining and heavy industry | Rugged devices for safety forms and inspections |
For a deeper look at shared and dedicated use, see the kiosk and dedicated devices and shared devices scenarios.
Setting up a kiosk in five steps
The details vary by MDM, but the process is the same.
- Choose the apps. Decide whether you need a single-app or multi-app kiosk, and make sure the apps work without access to settings. Test sign-in, permissions and printing before rollout.
- Create a kiosk policy. In the MDM, select the kiosk apps, the home screen layout if needed, and what stays visible, such as the status bar. Add the restrictions: no factory reset, no USB file transfer, no unknown apps.
- Enroll the device as a dedicated device. On a new or factory reset device, scan the enrollment QR code or use NFC or zero-touch. The MDM agent becomes Device Owner.
- Assign the policy. Put the device in the kiosk group. The apps install silently and the device switches into kiosk mode.
- Maintain remotely. Push app updates, change the policy and support users with remote screen control, without visiting the device.
A good test: restart the device, try the home and back buttons, pull down from the top of the screen and try to open settings. If any of these escape the kiosk, adjust the policy before rollout.
Common mistakes
- Forgetting system dialogs. Permission prompts or update screens can block a kiosk app. Grant permissions through the MDM in advance.
- No way to maintain the device. Make sure administrators can turn kiosk mode off remotely.
- Locking too much. If staff need the camera or a scanner app, include it in a multi-app kiosk instead of working around the lock.
How DeepManage does it
DeepManage kiosk mode uses Android’s lock task mode on devices where the agent is Device Owner. It supports single-app kiosks and multi-app kiosks with a custom home screen, can keep the status bar visible if the policy allows it, and returns to the kiosk after a restart. Kiosk mode is part of a policy, so you can switch a device in or out of it remotely, and support users with Live Control.