All articles
Devices

MDM and Android Enterprise: managing a fleet of driver tablets

May 22, 2026 The dropfleet team 8 min read
Share Post on LinkedIn WhatsApp
MDM and Android Enterprise: managing a fleet of driver tablets

Why MDM is essential from the very first professional device

Deploying a driver application on a tablet fleet without centralised management exposes you to an accumulation of small problems: a failed update on three devices, a driver who accidentally uninstalls the app, a Wi-Fi password changed without propagating to the field. Each incident is trivial in isolation; added up over a week of routes, they become a real source of operational friction.

MDM (Mobile Device Management) addresses this need for centralised control. In the Android ecosystem, it relies on the Android Enterprise programme and, more specifically, on the Android Management API for modern deployments.

Android Enterprise: the reference framework

Android Enterprise is Google's official programme for professional use of Android devices. It defines several deployment profiles depending on the nature of use:

  • Work profile: on a personal device, creates an isolated professional space alongside the personal space. IT manages only the professional part.
  • Fully managed device: company-owned device, entirely managed by IT. The employee can use it for personal purposes within the limits defined by policy.
  • Dedicated device (COSU): company-owned device, locked to a single use. This is the reference mode for delivery tablets.

For a logistics fleet, dedicated device mode — also called COSU (Corporate-Owned, Single-Use) — is the most appropriate. The device is fully managed, the driver app is the sole entry point, and the driver cannot access system settings or install other applications.

The Android Management API: enrolment and policies via server API

Until recently, managing Android devices in an enterprise context relied on the Device Admin API. This API is now deprecated by Google, according to the official Android Developers documentation: critical Device Admin features were progressively removed across successive Android versions.

The modern alternative is the Android Management API: a server-side REST API that allows devices to be enrolled, policies to be defined (permitted applications, network settings, system restrictions), and those policies to be deployed remotely across the entire fleet — without physically touching each device.

The enrolment flow works as follows:

  • The administrator creates a policy in the MDM console (or directly via the API).
  • An enrolment token is generated and transmitted to the device (via QR code, NFC link, or manual entry).
  • The device configures itself automatically: installation of permitted apps, application of restrictions, connection to the corporate Wi-Fi or VPN.
  • Any subsequent policy change is pushed remotely, with no field intervention required.

What you can manage remotely

  • List of installed applications (from Managed Google Play) and their silent configuration
  • Network restrictions: permitted Wi-Fi, enforced VPN, limited mobile data
  • Password and screen lock policy
  • Hardware restrictions: disabling camera, Bluetooth, USB storage
  • System updates: forcing an Android update within a defined maintenance window
  • Remote wipe in case of loss or theft

Managed Google Play: distributing without the public Play Store

Within Android Enterprise, applications are distributed via Managed Google Play. This enables you to:

  • Silently push an app to all enrolled devices, with no user action required
  • Distribute a private app (not published on the public Play Store) exclusively to your fleet
  • Manage versions and updates centrally

For a PWA driver app like dropfleet, distribution can happen directly via the managed browser, without even going through Managed Google Play — simplifying the update flow even further.

Which MDM solution to choose?

Several vendors offer MDM consoles compatible with Android Enterprise: VMware Workspace ONE, Microsoft Intune, Google Endpoint Management, Jamf, and open-source solutions. The choice depends on your existing ecosystem, fleet size, and available IT skills.

For logistics SMEs without a dedicated IT team, lightweight solutions — sometimes offered directly by the hardware manufacturer — allow you to get started without advanced expertise.

Integration with dropfleet

dropfleet is designed to operate in a managed Android Enterprise environment. The PWA driver app runs in the managed browser, route data are synchronised in real time with the dispatch console, and app updates are instant — with no driver action or store visit required.

Key takeaways
  • Android Enterprise defines three profiles: work profile, fully managed, dedicated (COSU)
  • The Android Management API replaces the deprecated Device Admin API for server-side fleet management
  • Managed Google Play enables silent app distribution without the public Store
  • Dedicated device mode is the reference profile for delivery tablets

Deploying a driver app on a managed fleet? Try dropfleet free for 14 days — no credit card, ready in 5 minutes.

Sources

This article is based on verifiable public sources:

  1. Android Developers — Dedicated devices overview & Android Management API
Enjoyed this article? Share on LinkedIn WhatsApp

Ready to transform your logistics?

dropfleet — multi-tenant SaaS logistics platform. No contract, no complexity.