Application Syncs

Application management is a key responsibility for device management. A fleet should run the same version of an application to create a uniform experience. In this article, we explain the types of applications and actions a blueprint takes to sync and maintain your device’s applications. 

In this article: 

• Understanding App Source Types
  • Types of Preload Apps
  • Source Types at a Glance
  • Enterprise Apps
  • Play Store
  • Special Cases
• Application Sync Scenarios
  • App Sync Modes at a Glance
  • Enforce Mode
    • Preloaded Apps (Enforce Mode)
    • Enterprise (Enforce Mode)
    • Play Store (Enforce Mode)
    • Kiosk Mode (Enforce Mode)
    • Locally Installed Apps (Enforce Mode)
    • Downgrade Scenarios (Enforce Mode)
    • App State Syncs (Enforce Mode)
    • Managed Config (Enforce Mode)
  • Do Not Enforce Mode
    • Preloaded Apps (Do Not Enforce Mode)
    • Enterprise (Do Not Enforce Mode)
    • Play Store (Do Not Enforce Mode)
    • Kiosk Mode (Do Not Enforce Mode)
    • Locally Installed Apps (Do Not Enforce Mode)
    • App State Syncs (Do Not Enforce Mode)
    • Managed Config (Do Not Enforce Mode)

Understanding App Source Types 

Depending on the source type, the application might be able to be updated or uninstalled. Likewise, if that application has a certain source type, it may be impossible to uninstall or specify its updated version.

Esper categorizes apps into three source types: 

• Preload: Apps pre-installed on a device. Sometimes referred to as System or Pre Side-Loaded apps. 
• Enterprise: Apps uploaded to the Esper Cloud and then installed on a device. 
• Play Store: Apps installed from the Play Store. Only available for GMS devices. You may need to approve these apps before being able to install them. 

When you create a blueprint, you specify which kinds of apps should be installed on the device, when they should be installed, and how they appear. However, some applications already come pre-installed on your devices. Other types of applications might not allow manual updates or uninstalls. 

We’ve laid out what happens for each source type when you attempt to install, uninstall, update, or downgrade these applications in Application Sync Scenarios. 

 You can check the applications installed on your devices in Devices & Groups > device > Apps. 

Types of Preload Apps 

Preload apps include all apps that come installed on a device. These apps might include System apps, such as Clock, and pre-side-loaded apps such as Google Chrome and YouTube. Once a device is provisioned, the Esper Cloud recognizes these apps as: 

• Can’t be uninstalled: System Apps cannot be uninstalled. 
• Uninstallable: Pre-side-loaded apps can be uninstalled. 

Apps installed through OS updates after provisioning will be considered Preload as well.

After a device is onboarded and provisioned, preloaded apps are hidden by default. 

Source Types at a Glance

There are advantages and disadvantages to both types of apps. 

Enterprise Apps 

Enterprise Apps are apps uploaded to the Esper Cloud, such as an application developed for your use case. They appear in the Enterprise tab of the Apps section. As an admin, you can specify which version of these apps appear on your devices through a blueprint. Because of this, they’re often easier than Play Store apps when it comes to controlling application versions. Apps installed locally are also considered Enterprise apps, such as those installed via the Device SDK or the API. 

Play Store 

Apps installed from the Google Play Store are Play Store apps. 

Special Cases 

Not all apps can fit neatly into one of the above categories. There are two special categories: 

• Enterprise-Preloaded: If a device comes preinstalled with an app at a higher version than the Enterprise app, then it is considered an Enterprise-Preload app. If removed from a blueprint, it will be brought down to the Preload version and its source type will be Preload. 
• Play Store-Preloaded:  If a device comes preinstalled with an app at a higher version than the Enterprise app, then it is considered a Play Store-Preload app. If removed from a blueprint, it will be brought down to the Preload version and its source type will be Preload. 

In the Application Scenarios section, you’ll see how a blueprint determines the actions and source types of these special applications. 

Application Sync Scenarios 

Blueprints determine the types of applications and versions on a device. Whenever the device interacts with the Esper Cloud, it syncs with its assigned blueprint. From there, it will execute the actions specified in the blueprint. 

App Sync Modes at a Glance 

How do blueprints sync different app types? The following scenarios explain what happens to applications before and after a blueprint sync based on the app sync mode. 

Enforce

When apps and versions are enforced, only the apps listed in the blueprint will be shown on the device. All other apps will be hidden or uninstalled. Some apps, such as sideloaded apps, are excluded from this behavior.

Do Not Enforce 

When apps and versions aren't enforced, apps listed in the blueprint, as well as those installed through Esper and from other sources, are shown on the device. Preloaded apps are hidden by default. 

Enforce Mode

The Enforce Sync Mode is available in a blueprint’s Apps & Configuration section. 

Use Enforce mode to lock down devices according to the apps defined in the blueprint. All other apps will be hidden or uninstalled based on the scenario. 

Preloaded Apps (Enforce Mode)

Enterprise (Enforce Mode)

Play Store (Enforce Mode)

Kiosk Mode (Enforce Mode)

The following scenario affects apps in Kiosk mode with any source type.

In this scenario, you’ll be prevented from saving a blueprint until you’ve chosen a new kiosk app or you’ve switched the blueprint to Multi-app mode.

 

Locally Installed Apps (Enforce Mode)

Apps can be installed locally if enabled through a blueprint. Once converged, these applications are considered Enterprise applications. 

If a locally installed app is updated locally, the application is considered an Enterprise app. 

Downgrade Scenarios (Enforce Mode)

Android does not natively support downgrades. However, Esper allows you to downgrade certain apps. The scenarios listed below are considered complex use cases that most users won’t run into every day. 

App State Syncs (Enforce Mode)

Converging devices also affects app state, meaning some apps will appear on the device, while others could be hidden or disabled. 

Managed Config (Enforce Mode)

A managed config is an app’s customizable settings. It may be set through a blueprint or from the device's app page. However, when a device converges with a blueprint, the managed config in the blueprint will take effect. 

Do Not Enforce Mode

This mode is available in a blueprint’s Apps & Configuration section.

 

When this mode is selected, the Esper-managed apps not listed in the blueprint will remain on the device, even if the currently converged blueprint does not mention them. For example, devices may install apps from a command, the API, or through a pipeline. These Esper-managed apps won’t be removed from the device through a blueprint converge action, but can still be removed manually. Basically:

• This mode is ideal for users who don’t want apps uninstalled or downgraded.
• Android devices on Esper Agent 8.0+ have access to this mode.
• Downgrades and uninstallations won’t happen in this mode. 

Preloaded Apps (Do Not Enforce Mode)

Enterprise (Do Not Enforce Mode)

Play Store (Do Not Enforce Mode)

Kiosk Mode (Do Not Enforce Mode)

The following scenario affects apps in Kiosk mode with any source type. 

In this scenario, you’ll be prevented from saving a blueprint until you’ve chosen a new kiosk app or you’ve switched the blueprint to Multi-app mode.

 

Locally Installed Apps (Do Not Enforce Mode)

Apps can be installed locally if enabled through a blueprint. Once converged, these applications are considered Enterprise applications. 

If a locally installed app is updated locally, the application is considered an Enterprise app. 

App State Syncs (Do Not Enforce Mode)

Converging devices also affects app state, meaning some apps will appear on the device, while others could be hidden or disabled. 

Managed Config (Do Not Enforce Mode)

A managed config is an app’s customizable settings. It may be set through a blueprint or from the device's app page. However, when a device converges with a blueprint, the managed config in the blueprint will take effect.