MobiLauncher

MobiLauncher

The launcher for the Android devices you issue your frontline and field workers. Sign up free, customize what the device shows, then deploy: install our native Android shell — it runs as a locked home screen and configures itself from an Android Enterprise / AMAPI managed-config push — or point your existing MDM at the URL we give you. Five minutes, no card.

What it is

MobiLauncher is the home screen for employee-dedicated Android devices — the company-owned handheld a worker uses as their primary tool for the shift. Field service technicians, retail associates doing line-busting, warehouse handheld operators, delivery and in-cab drivers: their device boots straight into a clean, branded launcher locked to exactly what the job needs, instead of stock Android. We host the launcher, you point your fleet at it, devices pick it up next time they sync.

It is not an MDM, and it doesn't replace yours. Your MDM enrolls devices, enforces policy, and pushes security updates — MobiLauncher doesn't compete with any of that. It owns the layer your MDM was never built to do well: the launcher the worker actually touches all day. Think value-add on top of the fleet you already manage.

The deployment backbone is our native Android shell — it runs as a locked HOME app under lock task and configures itself from an Android Enterprise / AMAPI managed-config push, so you need no third-party MDM. If you already run one, the same launcher URL drops right in:

  • Android Enterprise / AMAPI (recommended): push the app + its managed config from your EMM console — zero per-device touch, whole-fleet provisioning and re-pointing from one screen.
  • SOTI MobiControl: slots into a Lockdown Profile; SOTI's JS Agent API lights up the agent-action tiles (reboot / clear data / sync). One supported adapter, not a requirement.
  • No MDM / small fleets or pilots: sideload the APK and set the URL once (manual entry or QR). See mobicontrol-setup.md.

(The same engine will happily run a customer-facing screen — a self-service terminal or signage — too. That's supported; it's just not what MobiLauncher is built around.)

Pricing, honest

  • Free — genuinely free. No card, no trial timer, no upsell nag. One tenant, one config, hosted launcher URL, unlimited devices.
  • Pro — flat per tenant. Theming, multi-profile scheduling, signage mode, broadcasts, offline-first signed bundles, agent action tiles.
  • Enterprise — flat per tenant. Adds the OEM extension framework (Zebra MX, Samsung Knox, Honeywell EZConfig integration paths — per-OEM certification happens during beta onboarding), live remote config without redeploys, audit log, telemetry export.

Pro and Enterprise pricing finalizes before general availability — in public beta, amounts aren't published yet.

Yearly billing on both, knock ~15% off. No per-device count, ever.

Start here

Where to find us

Portal (signup, customize, billing): portal.mobilauncher.com Launcher demo: app.mobilauncher.com Support: mobilauncher@oakandashtech.com

These docs are written by the person who built MobiLauncher. If something's missing, wrong, or confusing, email and tell me — I'd rather fix the docs than answer the same question twice.