Skip to content

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, this cutting-edge software solution is designed to revolutionize the configuration of Android end-user devices (EUDs). By offering an automated approach, MANTLE Mobile eliminates the need for human intervention, ensuring swift, accurate, and scalable deployments across a spectrum of organizations.

Deployment Types

MANTLE Mobile supports multiple deployment methods to suit different use cases.

Ad-Hoc deployment is a flexible, on-demand method that allows users to deploy applications directly from the main GUI interface in the "Home" tab. Users can manage device configurations by selecting specific applications and configuration files for installation. This process involves selecting applications and corresponding config files, and initiating the deployment with a single click of the "Provision" button. Ad-Hoc deployments ensure that selected applications are installed in the order specified by the user. (See: Local Deployment)

Local Baseline Deployments offer a standardized way to manage application installations. Unlike regular Ad-Hoc Deployments, baseline deployments require the creation and import of a baseline file. This file dictates both the order of app installation and configuration settings, ensuring consistency across devices. Settings in the baseline file override any configurations set through Prep Manager during deployment. This type of deployment can be initiated from the "Baseline" tab from the Main GUI. (See: Local Baseline Deployment)

Enterprise Baseline Deployments are initiated from MANTLE Enterprise. All devices, applications, configurations, and baseline files (referred to as assets) associated with your group membership in the enterprise are synchronized to your local instance of MANTLE Mobile. (See: Enterprise Deployment)

Connection to MANTLE Enterprise is established by importing a token that assigns your instance to your enterprise group, completing the registration process. Once the connection is toggled on in MANTLE Mobile, assets automatically sync from the enterprise and remains connected, awaiting deployment instructions known as “Provisions.”

Workspace ONE Baseline Deployments follow the same requirements as Local Baseline Deployments but with a key difference: applications installed are based on those selected and listed in Workspace ONE using the Baseline Manager. For this deployment to succeed, both the MANTLE Mobile's host device (where the deployment is initiated) and the mobile devices must have connectivity to Workspace ONE. (See: Workspace ONE Deployment)

File Types

Understanding Configuration Files

Configuration files are written in JSON format and serve as instruction manuals for setting up and customizing applications on devices. They ensure that every device gets the same setup without manual intervention, providing consistency across multiple devices.

Purpose of a Configuration File

A configuration file is used to specify detailed instructions about how an application should be configured or set up during a deployment. This includes:

  • Application Details: Information such as the app name and version ensures that the correct application is being targeted.

  • Setup Steps: Detailed steps for setting up the application, including filling in fields with specific values and performing actions like tapping buttons.

For example, a configuration file might include instructions to:

  • Enter a server address or username in certain fields.
  • Click through specific screens during setup.
  • Set preferences and settings automatically based on predefined rules.

This file type is mandatory for all deployment types in MANTLE Mobile to ensure that every device is configured consistently and efficiently.

A Baseline File is a JSON file that is like a instruction manual that tells MANTLE Mobile how to configure your devices. This file includes detailed instructions about which applications should be installed and how they should be configured, as well as specific settings to apply on the devices.

Purpose of a Baseline File

A Baseline File serves several important functions:

  • Application Installation: It specifies which applications need to be installed on your devices.

  • Configuration Files: For each application, it includes references to corresponding configuration files that tell the app how to set itself up automatically. These configuration files ensure that all settings and preferences are pre-set according to specific requirements.

  • Device Settings: The file also contains instructions for setting various system settings on the device, ensuring that everything works exactly as intended from day one without any manual adjustments needed.

Key Components of a Baseline File

Application Installation Instructions
  • Specifies which applications should be installed.
  • Includes details about the version and source of each application (e.g., APK files).
Configuration Files
  • Provides links or references to configuration files for each application.
  • These configuration files contain detailed instructions on how to set up the application automatically, including user settings, preferences, and default configurations.
System Settings
  • Lists specific system-wide settings that should be applied to ensure optimal performance and security.
  • Includes details such as enabling or disabling certain features (e.g., Bluetooth, Wi-Fi), setting screen timeouts, and configuring other device-specific options.
Benefits of Using a Baseline File
  • Consistency: Ensures that all devices are configured in the same way, maintaining uniformity across multiple units.
  • Efficiency: Reduces the need for manual setup by automating the installation and configuration process.
  • Reliability: Minimizes human error and ensures that each device meets specific requirements without any inconsistencies.

Example Scenarios

Imagine you are rolling out a new fleet of tablets to your employees. Each tablet needs to have specific applications installed, such as email clients, document editors, and security software. The Baseline File would contain all the necessary information to install these applications automatically, configure them with predefined settings, and apply any required system settings (like disabling unnecessary features for security reasons).

A Baseline File provides a comprehensive set of instructions that streamline the setup process for devices by automating application installation, configuration, and system settings. This makes managing large numbers of devices more efficient and reliable, ensuring consistency and optimal performance across all devices.

An ATAK Pref File (Preference File) is a configuration file used in ATAK (Android Team Awareness Kit) to standardize settings across multiple devices. This feature ensures that all team members have identical user experiences, which is crucial for maintaining consistency and efficiency. This file type can be passed to the device during a deployment to quickly apply standard settings without manual adjustments.

Naming Convention - The pref file is named default and typically serves as the standard configuration for your organization.

Purpose of the Pref File - Standardization: A pref file allows you to save an ATAK configuration from one device and import it into other devices, ensuring uniformity. - Automation: It can automate the loading of ATAK plugins and set various preferences such as layout, colors, text size, toolbar settings, and unit measurements.

Example Scenarios

Imagine your team uses ATAK on devices that are shared among multiple members. You can create a pref file with all the necessary settings, such as imperial units for measurement and preferred toolbar layout. This pref file is then imported onto every device used by your team, ensuring consistency in user experience across all devices.

An ATAK Pref File allows you to save and import a standardized set of configurations to use across multiple devices. This ensures that all team members have a consistent user experience, enhancing efficiency and uniformity.

Terminology

  • Deployment: A Deployment is the execution of user-defined parameters upon connected devices. In MANTLE Mobile, deployments consist of applying Prep Settings, installing specified APKs, and executing Configuration Files. (See: How to Start a Deployment).

  • APK: An APK (Android Package Kit) is an installable application package for Android devices.

  • Configuration File: A Configuration File is a user-generated JSON document created via Record. It specifies an app’s name, version, and the list of tasks (e.g., button presses, text entries) to perform during a deployment.

  • Baseline File: A Baseline File is another JSON document, created in Baseline Management. It includes APKs to install, Configuration Files to run, and Prep Settings to apply for all devices in a deployment.

  • Record: The Record feature captures step-by-step actions on a single device to generate a Configuration File that can be reused on multiple devices.

  • Provision: A Provision refers to Deployments initiated from Mantle Enterprise.

  • JSON: JSON (JavaScript Object Notation) is the file format used by MANTLE Mobile for Configuration Files and Baseline Files.

  • API: An API (Application Programming Interface) facilitates secure communication between applications. In MANTLE Mobile, an API integration is used for Workspace ONE.

Key Features

MANTLE Mobile streamlines device setup and application deployment through the following capabilities:

MANTLE Mobile operates without internet access, making it ideal for air-gapped or otherwise restricted environments. This ensures secure, uninterrupted device configuration even in isolated networks.

MANTLE Mobile can configure multiple devices simultaneously—up to 12 at once per node—reducing deployment time significantly compared to manual methods.

By leveraging JSON-based Configuration Files, MANTLE Mobile automates complex application setups, removing repetitive manual tasks.

MANTLE Mobile goes beyond basic APK installation to allow for granular app settings, user prompts, and system configurations, providing a comprehensive solution for enterprise-scale deployments.