Mobile Application Management

How it works

Think of it as a supply chain with four stages. You source an app (public store, volume purchase, or your own build), you assign it to a group of devices or users, you configure it before the user ever opens it, and you retire it when the project ends.

Each platform exposes its own plumbing. Google routes everything through Managed Google Play, which has been the standard channel for Android Enterprise since 2017 and handles both public approvals and private app publishing. Apple uses Apps and Books in Apple Business Manager for volume licences, plus internal distribution for apps you never want on the App Store. The management server talks to both, so the admin works in one console.

Configuration is where the time savings show up. A managed configuration sends the tenant URL, the API endpoint and the SSO setting with the install, so the first launch already works.

Why it matters for a fleet

App sprawl creeps in quietly. A retail chain runs a stock app, a payment app, a staff scheduling app and a label printer driver. Multiply by 600 devices across 40 stores, add a version bump, and manual installs stop being an option.

There's a security angle too. Apps that arrive outside a managed channel can't be audited, can't be force-updated when a CVE lands, and don't disappear when an employee leaves. Managed distribution gives you an inventory you can actually trust, which is what an auditor asks for first.

How Appaloosa handles it

Appaloosa manages the app lifecycle end to end: an enterprise app store per organisation, public catalogues through Managed Google Play and Apple VPP, internal APK and IPA distribution with version history, managed app configuration, and silent updates on enrolled devices. Hosting runs in France on SecNumCloud-qualified infrastructure. See the Mobile Application Management page for the detail.