▦MobiLauncher

FAQ

Frequently-asked questions about MobiLauncher. Honest answers, including the limitations.

Pricing & licensing

Is it really per-tenant, not per-device?

Yes. One subscription covers every device on a tenant. We don't count seats. A fleet of 5,000 Zebra TC73s costs the same as a fleet of 50 — the per-tenant price is what it is.

What's the difference between Free, Pro, and Enterprise?

See the tier comparison for the full feature breakdown. Short version:

  • Free: one profile, basic 3-color theme, app/web tiles. Good for evaluating or small fleets that don't need theming.
  • Pro: full theming, multi-profile, schedules, signage mode, broadcasts, policy blocklist, agent-action tiles, diagnostic overlay, offline bundle.
  • Enterprise: everything in Pro plus remote config push, telemetry export, the OEM extension framework (Zebra MX / Samsung Knox / Honeywell EZConfig — per-OEM certification happens during beta onboarding), audit log.

(Pro and Enterprise pricing finalizes before general availability — we're in private beta, so amounts aren't published yet.)

Can I switch tiers later?

Yes. Upgrade via the Portal's Upgrade tab — Stripe-hosted checkout. Downgrade via the same flow's Manage subscription button (opens the Stripe Billing Portal); Pro features stop applying at the end of the billing period.

Is there a free trial of Pro/Enterprise?

The Free tier IS the trial. Every Pro/Enterprise feature renders in the Builder's live preview even on Free — you can see exactly what you'd unlock before committing. Only the on-device runtime enforces the tier.

Setup fees?

None. The monthly or yearly price is all-in. Pro Services (hands-on rollout help) is a separate add-on you can buy if you want it, but it's not required.

Deployment

Which MDMs do you support?

Verified production paths: standalone Android (sideload APK) and SOTI MobiControl Lockdown. These are what we run end-to-end today.

Should work, not customer-verified yet: Microsoft Intune, VMware Workspace ONE, Scalefusion, Hexnode, Esper, and any other kiosk-capable Android MDM. The launcher is a managed-browser homepage URL at heart, so the same kiosk pattern applies — we work with each beta customer to certify their specific MDM. See mdm-setup.md for the universal pattern.

If your MDM isn't here, email [email protected]. Adding a verified MDM is usually a one-call exercise.

Can I run this without an MDM?

Yes. The standalone Android APK (under "Sideload distribution" in mobicontrol-setup.md) wraps the launcher in a kiosk WebView. Sideload via adb, lock the device manually. Good for fleets under ~10 devices where an MDM doesn't pay for itself.

Does it work offline?

Pro+ offline bundles work fully offline once deployed — the launcher boots from file:// with no network round-trip. Hosted-URL deployments need a network to load the launcher on each boot. The launcher itself doesn't phone home for anything other than the optional broadcast poller (Pro feature, network-only) and the optional Enterprise telemetry export.

How big is the offline bundle?

Roughly 500 KB - 1 MB depending on the customer's inline assets (wallpaper, logo data URLs). The launcher's JS/CSS is ~150 KB gzipped; everything else is config and license.

Devices

Which Android devices are supported?

Anything running Android 7.0+ with a modern WebView (Chrome 80+).

Physically certified today: none. We don't have a hardware lab. The Builder's device-frame preview emulates the form factor + DPR of the rugged device families listed below so you can spot layout issues before you ship, but that's a layout preview — not a certification.

Device families targeted (Builder previews + designed-for):

  • Rugged tablets: Zebra ET40, Galaxy Tab Active Pro/Active5, Honeywell EDA10A
  • Rugged handhelds: Zebra TC73/TC22/TC52, Honeywell CT40/CT45/CK65, Galaxy XCover7/XCover6 Pro

Certification on physical hardware happens during beta onboarding — we work with the first customer (or the OEM directly) on each device family to validate the runtime on real devices.

What about iOS?

Not yet. We're Android-only. iOS Single App Mode could host a similar launcher experience but with significant limitations (no app-launch intents from a WebView, no MDM JS Agent equivalent). On the long-term roadmap, not a v1 priority.

Custom OEM hardware (barcode scanners, side keys, etc.)?

Enterprise tier includes the OEM extension framework — a plug-in architecture for vendor SDK integrations (Zebra MX/DataWedge/EMDK, Samsung Knox, Honeywell EZConfig). The integration paths are scaffolded so non-OEM fleets don't pay the cost.

The honest status: the framework is in place. We haven't validated any OEM SDK on physical hardware yet because we don't have the device families in-house. Certification on a given OEM is a beta-partnership conversation:

  • If you're a fleet operator with Zebra / Samsung / Honeywell / Datalogic / Bluebird / Panasonic / any rugged Android: we'd love to validate the SDK wiring on your devices together as part of beta onboarding.
  • If you're an OEM and want MobiLauncher certified on your device family — including ones we haven't listed — email [email protected]. Hardware loaners or remote-access labs both work.

Customization

How do I get my company logo on the launcher?

Portal → Theme tab → Branding & mode sub-tab → Logo field. Drag a PNG or SVG. We downscale to 256×256 PNG (preserving transparency) and inline it in your config. Pro tier required for the runtime to honor it.

Can the launcher use my brand colors?

Yes. Portal → Theme tab → Palette sub-tab. Free tier honors background / primary / accent. Pro tier unlocks the full palette (surface, text, text-muted) plus custom font, wallpaper, dark mode.

How do tile icons work?

Each tile picks from one of three icon sources:

  • Letter: auto-generated colored letter avatar (no config required)
  • Upload: drag-and-drop image, inlined in your config as a data URL
  • Asset ref: path to an image in your offline bundle

Mix and match per tile.

Can I push the same config to multiple device groups?

One config per tenant today. If different device groups need different launchers (warehouse vs delivery, day shift vs night shift), the common pattern is multiple profiles (Pro) with scheduled rotation between them. Schedules are cron-style, applied client-side.

If you genuinely need separate configs, run separate tenants. Per- tenant pricing means you can do this without per-seat math.

Operations

How do I push a config change to my fleet?

It depends on your deployment path:

  • Hosted URL: device fetches the config on every boot. Save in the Portal, devices pick up the change at next reboot.
  • Offline bundle (Pro+): re-download the bundle from the Portal, re-push via your MDM's File Sync.
  • Remote config (Enterprise): devices poll the config endpoint every 60s. Save in Portal → fleet updates within a minute, no reboot.

Can I send a fleet-wide message?

Yes — Portal → Broadcasts tab. Title, body, severity (info/warning/critical), optional start/expire times. Devices poll every 60s; the message renders in the launcher's bell-icon panel. Pro+ feature.

How do I see what's installed on a device?

The Diagnostic overlay (Pro feature) — long-press a configured corner of the screen on-device. Shows engine state, last config sync time, license tier + features, agent dispatch counters. Read-only; designed so support can ask the customer to screenshot it.

Do you collect telemetry?

The launcher does not phone home by default. Free + Pro tenants generate no outbound traffic except the optional broadcast poll. Enterprise customers can enable telemetry export to a sink they configure (their own endpoint, with retry + age-out). Privacy policy: privacy.md.

Building & extending

Can I customize the launcher's source code?

The renderer is closed-source today. Customer feature requests get prioritized via Pro Services engagements. If you have a hard integration need (custom OEM, novel agent action, embedded WebRTC client, etc.), email us with the scope.

Can I use my own backend for configs?

The hosted Portal is the easiest path. For Enterprise tenants who need to control the config-serving infrastructure (regulated environments, air-gapped fleets), the remoteConfig.poll endpoint is configurable — point it at your own server. The launcher still verifies the license signature against our Ed25519 public key, so spoofing tier upgrades isn't a thing.

Is the Builder open source?

No. The marketing site source ships in the same repo (you're reading docs that live in there) but the Builder / renderer / licensing server are proprietary.

Getting unstuck

Where do I report a bug?

Email [email protected] with: tenant ID, what you did, what you expected, what happened, plus a screenshot of the Diagnostic Overlay (Pro+) if you have it.

For Enterprise customers, you have a dedicated Slack channel — use that for production incidents.

Where's the status page?

status.mobilauncher.com. We publish API uptime + incident notes there. Subscribe to RSS if you want pager-style notifications.