EMM

How it works

An EMM suite stacks several layers. At the bottom, MDM enrolls the device and enforces OS-level policies. Above it, MAM distributes and configures apps, and can wrap or containerize them so corporate data stays inside. Then come content management (a secure document container), identity (single sign-on, certificates for Wi-Fi and VPN) and sometimes expense tracking.

The layers can be used independently. A contractor with a personal phone might get MAM only: the company's email app is managed, the device isn't. A warehouse scanner gets everything. A shared tablet at reception sits in between, with device management for the lockdown and app management for the two or three tools it runs.

Google made this layering concrete when it launched Android for Work in 2015, later renamed Android Enterprise. It defined explicit modes: work profile, fully managed, dedicated. Apple did the same with User Enrollment in iOS 13.

Why it matters for a fleet

The term helps you frame a buying decision. Ask "what do we actually need to manage?" and the answer is rarely "the device" alone. It's the apps, the data inside them, the credentials that reach the intranet.

Where EMM went wrong historically was complexity. Suites from the 2015 era bundled a dozen modules with separate consoles and licenses. Many teams paid for content management they never turned on.

Today the useful question is simpler. Does the platform cover the enrollment modes your device ownership models require (corporate, BYOD, shared), and does it distribute apps without friction?

How Appaloosa handles it

Appaloosa started as an enterprise app store and grew into device management, so both halves of EMM are native. The MDM layer handles enrollment, security policies, kiosk mode and remote wipe on iOS, iPadOS, Android, Windows and macOS. The app layer distributes public and private apps through Managed Google Play and Apple VPP, with contact and file sync alongside. Remote support runs on TeamViewer.