Locking down your devices with Workspace ONE Launcher includes the configuration of a profile and the deployment of the application to your device fleet. This profile allows complete customization of the look and feel of the device, and access to important settings and native applications depending on the app mode selected.
Workspace ONE Launchercan be configured in one of three app modes. Single App mode enables you to lock each device into a single app and prevent access to other features or settings on the device. You can provide access to dependent apps, set as hidden apps. Multi App mode enables you to restrict the Launcher profile to a limited set of whitelisted apps and customize the layout. Template Mode enables you to customize the entire user interface of the Launcher app such as app spaces, images, and text.
Using Workspace ONE Launcher with Android versus Android (Legacy)
How you use Workspace ONE Launcher depends on how you've configured setup in the Workspace ONE UEM console and the version of your Android devices:
- If you have completed Android EMM Registration and are using Android 6.0+ Work managed devices:
- Deploy Workspace ONE Launcherusing the Android profile. Using Workspace ONE Launcher with the Android profile configures devices for a single purpose such as kiosk mode by whitelisting supported internal and public applications. This hides certain settings on the device to prevent users from exiting from the Workspace ONE Launcher app. For more information on Workspace ONE UEM integration with Android, see the VMware AirWatch Android Platform Guide.
- If you opted out of Android EMM Registration with Google:
Deploy Workspace ONE Launcher using the Android (Legacy) method.
For more information on Workspace ONE UEM integration with Android (Legacy), see the VMware AirWatch Android (Legacy) Platform Guide.
After you configure all desired settings for your organization and selected app mode, determine what version of Workspace ONE Launcher you are pushing to our device fleet. You can control which devices receive the Workspace ONE Launcher by configuring the smart group assignment within the General profile when creating the Launcher profile.
Workspace ONE Launcher can be provisioned and deployed as a seeded application, internal application, or pushed through Product Provisioning. Depending on the use case for your device fleet, push the profile accordingly.
Using Custom XML in Launcher
Workspace ONE Launcher uses Custom Profiles to allow administrators to push advanced MDM features and other settings to Android devices using Workspace ONE Launcher that are not supported through the Workspace ONE UEM Console. The Custom Settings profile, as outlined in the Android Platform Guide, allows admins to enter their own XML into a profile and apply the profile to devices for custom settings.
Fore more information on how to configure Custom Profiles, see Using Custom Settings (Android).
For a complete list of available custom XML settings for Workspace ONE Launcher, see the following Knowledge Base articles per version: