Implementing Kiosk Mode on Zebra Devices: A Step-by-Step Guide

Kiosk mode restricts a device to a single purpose: users can't reach the Android home screen or recent-apps button, can't change settings like Wi-Fi or brightness, and can't exit the designated application. It's the standard setup for self-service terminals in transport and retail, order-taking tablets in hospitality, and enterprise handhelds where an employee should only ever see the app their job requires — the device stays stable and secure by simply not offering anything else.

Implementation Options

• Lock Task Mode — Android's own official API since version 5.0; easy to implement and gives control over individual features like the home or back button, but limited to Android 5.0 and later.
• App pinning — a built-in Android setting, no development needed, but it only supports one app and a user who knows the trick can easily bypass it.
• Third-party solutions — tools like Zebra's Enterprise Home Screen offer more functionality than the native options and centralized management, at the cost of being tied to specific manufacturer devices.

Zebra's Own Tools

Zebra offers three tools for this: Enterprise Home Screen (EHS), a user-friendly, ready-made launcher replacement; StageNow, which supports complex configuration including Wi-Fi and security customization; and Zebra Mobility Extensions (MX), the most advanced option, working directly at the device level. EHS replaces the entire user interface with a customized one that only exposes the applications an administrator has approved — but it comes with a real warning: if you set EHS as the home app and make that selection permanent, you can lock yourself out of the device, since file system access and USB debugging stop being available once that's done.

Configuration and Its Risks

EHS is driven by an XML configuration file, enterprisehomescreen.xml, retrievable over ADB once the app is installed. Turning kiosk mode on means adding the target app inside a <kiosk> tag, setting kiosk_mode_enabled to 1, and — critically — leaving usb_debugging_disabled at 0 while you're still testing.

For teams that don't need the full lockdown, EHS also supports a dual-login mode that separates an Admin profile from a User profile, so administrators can control which apps are available while leaving day-to-day operation flexible.