Some AppMgr functions apply only to System apps, some only to User apps, and some to both. User applications are not built in, and must be installed before use. System applications are built into the device and always by default. When considering the capabilities of AppMgr, it is important to understand the difference between System apps and User apps. 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.
On consumer Android devices, app management generally requires the user to interact with a management UI presented on the device. 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.
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. The Device Model indicates which subset of MX features is present in the device.Īpplication Manager (AppMgr) administers the user applications on the device.Others require a specific MX version plus a minimum version of Android. The Android version is sometimes enough to determine a feature set.Some features require a specific pairing of MX and OSX versions. The MX Management System provides a uniform interface into privileged and unprivileged Android APIs on the device.The root OSX version number always matches the root number of the Android version that it extends. The OSX layer provides extensions to the base operating system to implement functionality not offered by Android.OSX, MX and Android version information for a device can be found in the Android Settings panel or by querying the device through ADB, EMDK or the MX CSP. To clear all selections press the SmartDocs button.Click the forward and back SmartNav buttons to scroll to the next and previous supported feature of that CSP (SmartNav is not supported on the feature matrix). "App Manager") and make at least one selection in the SmartDocs bar. SmartDocs Nav works when viewing features of an individual CSP.
Unsupported features turn gray based on selection(s).