Software Payload

Use software payloads to distribute apps to smart devices. The payload sends the app information and location to devices for installation.

You can distribute an app hosted in an app store or host the application files through Avalanche. When the app is in an app store, the device displays the page where the user can download and install the app. When the applications files are hosted through Avalanche, the device downloads the file from the specified location and begins installing the app.

You can create a new software payload that overwrites any previously existing payloads for the same software. It will remove the old version and install the new application version without impacting existing configurations.

Android

A software payload for Android devices may have the following options, depending on where the app is hosted:

Payload name	The name of the payload.
App hosting	The location hosting the software. •Google Play store. Select this option if the app is available through the Google Play store. •Manifest URL. Select this option if the app is available through a URL or is stored on the Central File Store. Silent app deployment to Samsung SAFE devices does not support Google Play apps and can only be performed using the Manifest URL option.
Google Play store	Store URL. The URL for the application in the Google Play store. Click Browse to perform a search of the Play Store.
Manifest URL	Manifest URL. The URL for the app .apk file. You can also search for a specific manifest URL by clicking the search icon. This displays all hosted .apk files on the Central File Store. Click the file you want to use and click Select. Once selected, the app data will populate the Package ID and Package Version fields. Package ID. The name of the application, also known as the bundle ID or package name. For a custom app, the developer can tell you what the package ID is. As an example, the package ID for Google Maps is: com.google.android.apps.maps Package Version. The version of the package. Prerequisite Apps. The apps that must be installed before installing the app delivered by the payload. If the prerequisite apps are not on the device, the installation will fail. This option only applies to manifest URL hosted apps. •Package ID. The package ID of the prerequisite app. •Operator. Defines the required state of the prerequisite app. If the exists option is selected, any version of the app is sufficient. All other options relate to the version entered in the Version field. •Version. If an operator other than exists was selected, defines which version the operator relates to. To use manifest URL distribution with the Samsung or universal enabler on Android 8+, ensure you grant the enabler permission to install apps from unknown sources during installation.

Android Enterprise

Devices managed through Android Enterprise download apps from the managed Play Store associated with the enterprise they enrolled with. Once you have created an enterprise, you can log into the managed Play Store to approve, purchase, and publish apps.

Once an app has been approved, purchased, or published in an enterprise's managed Play Store, it will appear in the managed Play Store. Enterprise apps can also be configured and distributed to Android Enterprise managed devices with software payloads.

The following types of apps are available through the managed Play Store:

•Normal apps. Approve normal apps in your managed Play Store.

•Paid apps. Purchase application licenses through your managed Play Store. View how many licenses you have remaining on the My Managed Apps tab of your managed Play Store.

•Private apps. Distribute private apps by publishing them to your managed Play Store. Apps published this way will only be available within your enterprise.

Software payloads for Android Enterprise devices have the following options:

Payload name	The name of the payload.
Enterprise Service Account (ESA)	Select which Android Enterprise's managed Play Store the app will be downloaded from.
Enterprise App	Click Browse to see a list of approved applications in the selected enterprise Play Store. You can select an app from the list or search for a specific approved app.
Current Configuration	Some apps in the managed Play Store offer managed configuration. Available configurations vary by app. For more information, see Configuring Enterprise Apps. Managed configurations give you access to OEM configurations from some device manufacturers. For information about available configurations and how to set them up, see OEM Configurations.
Runtime Permissions	Configure permissions for the selected app. Select Grant, Deny, or Default for each requested permission. Selecting Default will set the permission to use the default option selected under Tools > Android Enterprise. For more information, see Setting Enterprise App Permissions.
Launch after install	(Optional) Launch the app after installation. This option is important for installing remote control software. For more information, see Installing Splashtop Components.
Launch after reboot	(Optional) Launch the app each time the device is rebooted.

iOS

Payload name	The name of the payload.
App hosting	The location hosting the software. •AppStore. Select this option if the app is available through the Apple App Store. •Manifest URL. Select this option if the app is available through a URL or is stored on the Central File Store.
AppStore	App. The URL for the application in the Apple App Store. Click Search to perform a search of the App Store.
Manifest URL	Manifest URL. The URL for the app .plist file. The URL must us HTTPS. Bundle ID. The identifier specified in the app manifest file. For example, the ID for the Avalanche app is 418167706. Bundle Version. The version of the bundle. If this number changes, the software on the device is updated.
Configuration Data	If the app is designed to accept configuration data as key-value pairs, use this section to configure the app. Click Add Key to add key value pairs provided by the app developer. When the payload is installed on a device, the app can automatically use the configuration data.