UEM

How it works

Gartner started using the term around 2017, when it merged its Magic Quadrants for client management tools and enterprise mobility management. The idea was pragmatic: Windows 10 and macOS had gained MDM-style management APIs, so the same server could manage a laptop and a phone through the same protocol.

A UEM platform therefore speaks several dialects. Apple's MDM protocol for iPhones, iPads and Macs. Android Enterprise for Android. The Windows MDM CSPs (and often a co-management bridge to Intune or Configuration Manager) for PCs. On top sits a shared layer: user directory, compliance rules, app catalog, reporting.

In practice, "unified" is a spectrum. Some products manage Macs deeply and Windows superficially. Others do the opposite. Rugged Android scanners, which often run older OS builds, are a third case: check that the vendor tests on the Zebra or Honeywell models you actually deploy.

Why it matters for a fleet

If your fleet is 300 iPhones and nothing else, UEM buys you little. If it's 300 iPhones, 80 Android scanners in the warehouse and 150 MacBooks in the office, running three consoles means three inventories, three onboarding scripts and three places to check when the auditor asks which devices are encrypted.

The other argument is security posture. A conditional access rule that says "only compliant devices reach the CRM" only works if every device type reports compliance to the same place.

But don't buy the label. Ask what the product does on each OS you actually have.

How Appaloosa handles it

Appaloosa manages iOS, iPadOS, Android, Windows and macOS from a single console, which puts it in UEM territory for most fleets. Zero-touch enrollment works through Apple Business Manager, Android zero-touch and Windows Autopilot, and the same security policies, enterprise app store and remote wipe apply across platforms. You'll find the platform coverage on the Mobile Device Management page.