Enterprise app store

How it works

The store is a managed front end on the device, fed by the management console. An admin approves a public app, uploads an internal build, or adds a web app, then assigns it to a group: warehouse, sales, store managers. The catalogue on each device shows only that group's entries.

Behind the scenes, the installs use the platform channels. Android pulls approved and private apps from Managed Google Play, so the binary is signed, scanned and delivered by Google even when the app never appears publicly. On iOS and iPadOS, volume licences come from Apps and Books in Apple Business Manager, and in-house builds are distributed internally to enrolled devices.

Two deployment styles coexist. Required apps install silently, before the user opens anything. Optional apps sit in the catalogue and wait, which suits tools only part of a team needs. Most fleets mix the two: five required apps, a dozen optional ones.

Why it matters for a fleet

It removes the APK-by-email habit. No shared download link, no "install from unknown sources" toggle, no uncertainty about which build someone actually ran.

It also cuts support calls. A technician on a site with no signal opens one icon, taps the app, and gets the right version with the right settings. Compare that with a phone call explaining where to find a link in a six-month-old email thread. And for the admin, the store doubles as an inventory: who has what, in which version, since when.

How Appaloosa handles it

Appaloosa's enterprise app store is the centrepiece of the product. Each organisation gets its own catalogue with public apps via Managed Google Play and Apple VPP, private APK and IPA distribution with full version history, per-group assignment, required or optional installs, and managed app configuration applied at install time. Details on the Mobile Application Management page.