The custom Android Launcher is one of the most demanded features in a mobile device management solution. Its main function is to create an interface that acts as a cover, allowing the user to access only the applications authorized by the company. In addition, it has the option of blocking the notification bar, avoiding the possibility of “leaks”.
Until a few days ago, cloud4mobile only offered the launcher option for Samsung and LG devices, using special APIs. Now it’s officially available version that extends the features to suit any Android device.
See more about the Samsung special features for cloud4mobile (in portuguese).
Without further ado, let’s explain below with a step by step, how to configure your Android launcher:
We assume that you already have an account on cloud4mobile. If this is not your case, click here to create a free account to manage up to five Android devices. Once this is done, click on the ‘add device’ menu and follow the steps below:
Step 1: Installing the applications
To run all features, you must install two applications on each device that will be managed. This step is required only once, at the time of deployment. Once installed, all updates will automatically occur through the Google Play Store.
The applications are:
This is the main application to be installed. It is he who will assume the role of administrator of the device, allowing you to perform all the settings and management from the Operations Console. To use, perform the device enroll by typing the code reported by cloud4mobile directly into the MDM Agent.
Note: The free account gives full access to features for up to five devices. Thus, it is possible to perform all the tests already in the production environment.
Cloud4mobile Android Launcher
Just install the application because the rest of the process will be done through the Operations Console, as we will see next.
With both applications already installed and communicating with the system, on all managed devices, we are going to launcher configuration step.
Step 2: Creating groups
In the Operations Console, click on the ‘Groups’ option in the left side menu. Select the ‘Create Group’ option and name the group according to your interest, as shown below:
If desired, create related subgroups for each policy pattern that you want to apply. For example, the SP Sellers group may have a subgroup Sellers Region ABC. It makes sense to create new groups and subgroups whenever they require a different set of applications and features. The group allows you to apply policies or manage application usage in batch operations.
Step 3: Setting up the profile
After the group is created, click on the ‘Profiles’ menu on the left side. Click on the ‘New Profile’ button on the right side, after, select the ‘Launcher Android Configuration’ option and click ‘Next’. See the example below:
Now configure your profile by setting a password type, background image, and authorized applications. The dynamic password is automatically changed every day. This is the launcher’s exit password. Therefore, the dynamic option reduces the chance of the password being discovered by the user. The static password is set by your system administrator and can be changed manually whenever you want.
Note: One of the novelties of this version is the ability to block access to the notification bar of the device. As a result, access to settings is inaccessible.
Already the background image can be customized with the company brand, for example. In this case, just select the ‘custom’ option and apply the image in both the vertical and horizontal versions, according to specifications. Do not forget to apply the settings before proceeding.
The whitelist will display all apps that will be automatically loaded to groups that use that profile. If you already have a linked device, with all the applications you want to use, you can import applications from it. If you prefer, you can manually add your corporate apps. Everything that is entered in this whitelist will be displayed to the user. Other applications that are installed on the device will continue there but will not be accessible. If the user finds a way to get to it and clicks to open, the launcher will automatically overlap to prevent access.
After that, go ahead, name your profile and save. Do not forget to associate the devices on which you want to apply the profile. This can be done in batch by selecting the devices on the home screen.
Your launcher is set up. Repeat the process by adjusting the settings for as many profiles as you need, and isolate the business applications. More safety, more productivity and longer device life are just a few of the benefits.
Note: Before delivering the device to the employee, clear the application and configuration access memory. So it will not be able to access anything that is not applied to the cloud4mobile MDM Launcher.
If you have any questions, our team will be at your disposal!