Kiosk mode: lock your delivery tablet to a single app

The problem kiosk mode solves

Picture this: a driver mid-route accidentally closes the delivery app, ends up on the home screen, and spends several minutes trying to get back to his route. Or worse: he accidentally factory resets the tablet while trying to change a setting, losing all unsynced local data. These are not hypothetical scenarios — they happen in any fleet that has not secured its devices.

Kiosk mode (or dedicated mode) in Android Enterprise addresses exactly this problem: it locks the device to a single application and removes access to the home screen, system settings, and any other app.

Android dedicated mode: the technical foundation of kiosk mode

In Android Enterprise terminology, kiosk mode corresponds to the dedicated device profile (or COSU — Corporate-Owned, Single-Use), according to the official Android Developers documentation. A device in dedicated mode is a fully managed Android device for single use: the organisation controls entirely what the user can see and do.

Concretely, this mode enables the following:

• The designated application (e.g. the dropfleet driver app) launches automatically when the device starts.
• The Home button and Recents button are disabled or redirect to the application.
• The notification bar is hidden or restricted.
• Access to system settings is blocked for the user.
• Installing new apps is impossible without administrator authorisation.

Managed Google Play: distributing the app in kiosk mode

Deploying the application in kiosk mode goes through Managed Google Play, Android Enterprise's application distribution platform. The administrator publishes or references the driver app there, associates it with an MDM policy, and silently pushes it to all enrolled devices.

For a PWA (Progressive Web App) like the dropfleet driver app, distribution can happen via the managed Chrome browser — without going through the Play Store or Managed Google Play. The app URL is configured in the MDM policy, and the app opens automatically on every boot.

Hardware locking: protection against factory reset

A point often overlooked in kiosk deployments: Factory Reset Protection (FRP). Without prior configuration, an unauthorised or confused user could attempt to reset the tablet via the recovery menu, bypassing the software lock.

Android Enterprise addresses this risk via hardware locking: in dedicated device mode managed by the Android Management API, a factory reset requires Google administrator credentials to re-enrol the device. Without those credentials, the tablet remains unusable for anyone who tries to misuse it.

What kiosk mode changes day to day

For the driver, the experience is simple and frictionless: switch on the tablet, the app is there, and it stays there. No unexpected updates mid-route, no notification from another app diverting attention, no risk of accidentally modifying settings.

For the dispatcher and logistics manager, it is the guarantee that every device in the fleet behaves identically and predictably. App updates are deployed remotely outside driving hours and applied silently on the next boot.

Limitations to be aware of

• If the app requires a network connection, a dead zone can block all interaction. An offline mode is essential (see our article on field connectivity).
• Kiosk mode blocks system settings access but does not replace a network security policy (VPN, data encryption).
• In the event of a critical app bug, the administrator must be able to intervene remotely or physically — plan this scenario in your maintenance strategy.

Setting up kiosk mode with dropfleet

dropfleet is designed to run in kiosk mode on Android Enterprise. The PWA driver app launches in the managed Chrome browser, configured in kiosk mode by the MDM policy. No store installation is required, and app updates are transparent for the driver.

Secure your field tablets today. Try dropfleet free for 14 days — no credit card, ready in 5 minutes.