Application Manager (AppMgr) administers the user applications on the device. It can be used to programmatically install, uninstall, upgrade and turn on (or off) the ability to launch an application, all with no need for user interaction. AppMgr also can designate an application as the Default Launcher (invoked when pressing the HOME Key), and can perform other tasks related to the management of applications.

On consumer Android devices, app management generally requires the user to interact with a management UI presented on the device. For corporate scenarios involving management by an Enterprise Mobility Management (EMM) system (sometimes referred to as mobile device management, or MDM), user consent or approval might not be desired as they potentially limit a company's ability to fully control the user apps installed on a device. AppMgr provides such control.

When considering the capabilities of AppMgr, it is important to understand the difference between System apps and User apps. System applications are built into the device and always by default. User applications are not built in, and must be installed before use. Some AppMgr functions apply only to System apps, some only to User apps, and some to both. Each function identifies the class of the app(s) to which it applies.

Main Functionality

Package names can vary from one Android version to another.

GMS Restricted Mode: In response to security concerns, Zebra has implemented GMS Restricted Mode, which allows administrators to disable some or all GMS apps deemed "safe to disable" without interfering with normal device operations. See GMS Manager for more information.

Android File Security

Zebra strongly recommends using Secure Storage Manager for on-device file sharing and persistence. SSM provides greater security than the legacy /enterprise partition method and aligns with Google's long-term strategy for Android security.

For administrators, Secure Storage Manager processes are similar to those of legacy methods. For example, where the legacy method uses an on-device path for file deployment, SSM employs a URI specific to the sharing app. For complete instructions, see the StageNow guide Using SSM with AppMgr and FileMgr.

App Permissions

The evolving security practices employed by Android have changed the user experience in Android 10 to give greater control to the device user. Such changes could impact the enterprise use cases of Zebra customers. To implement the necessary functionality while maintaining device security, MX 10.0 provides the IT administrator with the ability to silently (without device-user interaction) grant application runtime permissions typically used by remote management systems. For some of the Actions executed by this CSP, including Install and Upgrade, apps must be targeted at Android API level 23 (or newer) to be silently granted runtime permissions on devices running Android 10 or later.

Battery Optimization

The App Manager allows one or more apps to be added to the Battery Optimization "exemption whitelist." While running, apps on this list prevent the device from entering Doze and App Standby power saving modes, thereby preserving their ability to continue functioning and/or providing services. Doze mode conserves battery power by deferring background CPU and network activities when the device is idle. App Standby defers background network activity for apps with which the user has not recently interacted. By default, all non-system apps are subject to Doze and App Standby modes unless added to the whitelist.

For more information, refer to the Android Developer site.

Virtual Keyboards

Virtual keyboards (aka soft input panels) are enabled and disabled by referenceing their package name with the desired AppMgr Action. Some of the most common keyboards are listed below: