MAM

How it works

MAM sits on top of what the operating system exposes. On Android, the admin approves apps in Managed Google Play and pushes them into the work profile or onto a fully managed device; the install happens silently, with no Google account prompt and no store browsing. On iOS and iPadOS, apps bought through Apple Business Manager or distributed internally are installed as managed apps, which means the MDM owns them and can pull them back.

Two mechanisms do most of the work. Managed app configuration ships settings with the app, so a field technician never types a server URL. And managed open-in rules decide whether a document can move from the corporate mail client into a personal cloud drive.

A common confusion: MAM is sometimes sold as a device-free alternative, where a container wraps each app. That approach exists, but it needs an SDK or app wrapping, which means the app vendor has to cooperate. Most fleets get better results combining enrollment with app-level control.

Why it matters for a fleet

Hardware is the easy part. The painful part is the 14 apps your warehouse team needs, two of which are built in house and updated every month.

Without MAM, somebody emails an APK link, users install it by hand, and six months later nobody knows which version runs where. With MAM, you push version 3.2 to 400 devices overnight and check the install report in the morning. When someone leaves, the work apps and their data go, and the device stays usable.

How Appaloosa handles it

Appaloosa gives each fleet an enterprise app store carrying both public apps (through Managed Google Play and Apple VPP) and private ones: your internal APKs and IPAs, uploaded, versioned and assigned per group. Settings travel with the app through managed app configuration, and removal is a single action. The full scope sits on the Mobile Application Management page.