Mantle-Mobile Overview

Mantle-Mobile directly addresses the challenges of deploying Android devices and applications at scale. Recognizing the pain points in traditional manual processes, it replaces hands-on configuration with automation that enables fast, accurate, and scalable deployments across organizations.

If you need…	Go to…
Installation and licensing steps	2. Getting Started
UI tour and menu descriptions	3. Menus and GUI
Baseline authoring workflow	6. Building Baseline Files
Mantle 2.0 enterprise integration	8. Mantle 2 Integration

Start Here: Core Concepts

• Configuration File: JSON task list used to configure an app on the device
• Baseline: JSON bundle of prep settings, APKs, and configs
• Provision: Execution of a baseline against selected devices
• Connected Device: USB-attached device visible in Connected Devices
• Device Database: Devices stored in the encrypted database and eligible for workflows
• Node Mode: Enterprise-driven automation used when Mantle Mobile registers with Mantle 2.0
• Token Count: Maximum allowed managed device count based on license
• Prep Tasks: Android settings that are set at the start of a provision

Workflow Architecture

Provisioning succeeds only when the underlying data is ready. Ensure the following four items are complete before you run your first job:

• Devices imported into the local database
• Assets (APKs, Unique Files, ATAK prefs) uploaded and verified
• Configuration files recorded or imported
• Baseline assembled from OS prep settings, APKs, and configurations.

flowchart LR
    D[Connected Devices] --> P[Provision]
    A[Assets: APKs, Prefs, Files] --> B[Baseline]
    C[Application Configurations] --> B
    T[OS Prep Tasks] --> B
    B --> P
    P --> R[Track Provision Status]

How the Pieces Relate

A baseline is the orchestrator. It references the prepared assets and defines the order of execution.

• Prep Tasks: Android settings applied before apps launch
• APKs: packages to install on every targeted device
• Configurations: recorded task lists that drive in-app setup
• Provision: executes the baseline for every eligible device and tracks status in real time

flowchart TD
    Prep[OS Prep Tasks] --> Baseline
    APKs --> Baseline
    Configs --> Baseline
    Baseline --> Provision
    Provision --> Logs

End-to-End Path

1. Initialize the app and set the encryption key.
2. Upload a valid license (Settings > Licenses).
3. Connect devices (USB debugging enabled) and import them into DEVICE DATABASE.
4. Import assets (Assets) and record or refine configs (Create > Create Config).
5. Build a baseline (Create > Create Baseline).
6. Execute the baseline (Provision) and monitor progress (Track Provision).

Common blockers

Provisioning fails most often when devices are not imported, required APKs are missing, or configs are recorded but never added to a baseline. Use the dependency chain Devices → Assets/Configs → Baseline → Provision → Logs to troubleshoot.

Navigation Model

This release uses a left sidebar with the following top-level sections:

• Create (Create Config, Create Baseline)
• Devices
• Enterprise (license-gated)
• Assets
• Provision
• Settings

See Menus and GUI for detailed page-by-page behavior.

License and Access Notes

• Enterprise pages are blocked when no valid license is installed.
• Device Count/token limits are enforced by the installed license.
• Unlicensed use is limited to recording configuration files and building baselines. Default Token count is 2.