Using Third Party Launchers

Using a third-party launcher instead of the Esper Launcher or default Android launcher? You can set a third party launcher from a blueprint. 

Note: Devices not using the Esper Launcher may have limited access to device management features, such as layout customization.

Requirements: 

• Android devices on Esper Agent v9.4.3188+

Setting the Launcher

Step 1: Adding the Launcher App

In Apps > Esper Android Apps, upload the launcher app as an APK. 

Step 2: Setting Up the Blueprint

In a new or existing blueprint, set the launcher type to Android Launcher.

Then, add the launcher to the blueprint’s application list. Set the following: 

• Launch on Start: Disabled 
• Installation Rule: During Provisioning
• App State: Show

Step 3: Add the dpcParam to the Blueprint 

Enable the blueprint’s Esper Settings > Advanced Android Settings > Enable JSON. Then paste the JSON. 

Include the following: 

• packageName: the launcher app’s package name. 
• activityName: the launcher app’s activity name. Often MainActivity. 

{
    "dpcParams": [
        {
            "key": "setDefaultLauncher",
            "value": "{\"packageName\":\"com.app.packagename\",\"activityName\":\"com.app.launcher.activity.main.MainActivity\"}"
        }
    ]
}

Then save, publish, and converge the device to the blueprint. Ensure the converge is successful by checking a few devices’ Event Feeds.

Clearing the Launcher

In the blueprint’s Esper Settings > Advanced Android Settings > Enable JSON, replace the setDefaultLauncher key and value.

{
  "dpcParams": [
    {
      "key": "setDefaultLauncher",
      "value": "{\"clear\":true}"
    }
  ]
}

You can then optionally remove the launcher app from the blueprint’s app’s list.

Once the blueprint is converged, the device will launch using your specified third-party launcher. To switch launchers, update the dpcParam values and reconverge.