Lock a single app as the permanent interface using Kiosk Mode (Blueprint)

Android

Kiosk Mode locks your Android device to run a single app permanently, surviving reboots, power loss, and app crashes. Users cannot navigate away or access the home screen. This guide explains how to set up Kiosk Mode using a Blueprint in the Esper Console.

Before you begin

Kiosk Mode is useful for devices deployed as single-purpose terminals, such as:

Point-of-sale (POS) systems
Digital signage displays
Self-service kiosks
Lobby displays

Ensure your Esper subscription tier includes Kiosk Mode and that your devices are already enrolled in Esper.

How to enable Kiosk Mode

Open the Esper Console and navigate to Blueprints. Create a new Blueprint or edit an existing one that you want to apply to your device group.
In the Blueprint editor, locate the Kiosk Mode section (typically found under Apps & Configuration or Device Settings).
Enable Kiosk Mode and select the app you want to pin as the kiosk app. This automatically configures the app as your device launcher.
Verify the target app is added to the Blueprint's app list and set to Auto-launch on boot if that option appears separately.
Save the Blueprint.

How to apply Kiosk Mode to your devices

In the Esper Console, navigate to Devices & Groups and select the device group where you want to apply the Blueprint.
Go to Blueprint and assign your Kiosk Mode Blueprint to the group.
Click Reconverge to push the configuration to all devices in the group at once. No per-device action is required.
Wait for the reconverge to complete. Devices will receive the policy once they are online.

How to verify Kiosk Mode is working

On a test device, perform the following checks:

Reboot the device and confirm it boots directly into the pinned app.
Press the Home and Back buttons to confirm navigation controls are suppressed.
Force-close the app and verify it relaunches automatically.

Troubleshooting

The app doesn't relaunch after a crash:

Verify the app is correctly set as the kiosk/launcher app in the Blueprint.
Check that the Blueprint status shows Compliant on the device after reconverge.

Users can still navigate away from the app:

Confirm the Esper Device Agent is active and up to date on the device. Outdated agents may not enforce all Blueprint policies.

The device is still non-compliant after reconverge:

Ensure the device is online during reconverge. Offline devices will receive the policy once they reconnect.

Kiosk Mode is not visible in the Blueprint editor:

Verify your Esper plan includes Kiosk Mode. This feature may vary by subscription tier or device enrollment type.

Kiosk Mode is enabled and the device shows Compliant, but the app is still exitable:

Some devices (particularly certain MediaTek-based tablets) may have system-level restrictions that limit launcher replacement. Test on representative hardware before fleet deployment.

Additional options

Kiosk Mode can work alongside other device restrictions. If you want to prevent status bar pull-down, volume keys, or power button access, configure these options in the Blueprint's Kiosk Mode or Device Settings sections.

Still need help?

If you're still experiencing issues with Kiosk Mode, contact Esper Support and provide the following details:

Device model and Android version
The app you're trying to pin
Whether the device shows as Compliant in the Esper Console
Whether the device was online during reconverge