Project

General

Profile

Actions

Improvement #10414

open

Change the flow of installing a Android Enterprise App

Added by Arshana Atapattu 11 months ago. Updated 3 months ago.

Status:
New
Priority:
Low
Assignee:
-
Start date:
29/10/2023
Due date:
% Done:

0%

Estimated time:
Device Type:
Component:
Type:
Platform

Description

Description

Currently Android Enterprise apps are installed in a complicated manner1.
Need to change the flow of installing a AE app for better user experience.
(Should be able to install the app directly from app store)

[1] current way of installing a android Enterprise app(Refer video for more information)
Steps:
Create a Android Enterprise App
Create a group(Existing group is ok)
Add the device/s that are need to install AE app in to the group
create a policy or modify a policy including "Enrollment Application Install" policy and adding that AE app in to that Enrollment Application Install policy.
When creating policy select the group you need to install the AE app.
Apply policy.


Files

apply policy and install app.mkv (8.19 MB) apply policy and install app.mkv [1] Arshana Atapattu, 29/10/2023 06:51 AM
Actions #1

Updated by Inosh Perara 11 months ago

  • Priority changed from None to Low
Actions #2

Updated by Viranga Gunarathna 11 months ago

Suggested new flow

When publishing an Android Enterprise app via App Publisher, we can store a default version of app configurations. Whenever we push the app via the App Store (without having specific configs via a policy), the app takes the default app configurations and pushes them to the device. If users need to make custom app configurations regarding that app, they can enable the Enrollment App Installation(EAI) policy to add customized configurations.

When we are pushing an Android Enterprise app to a device on which the EAI policy is already enabled, we can overwrite these app configurations. We should separate out which app configurations (Default configs coming from app store installation or customized configs coming from the policy) need to be used in that particular device.

When the same app is in the EAI policy with different configurations, we can apply the configurations from the policy, instead of the app. If the device is compliant with the policy, we can overwrite the default configurations and enforce the configurations we push through the policy.

We can show the same UI in the App Store as well to change the default app configurations. If someone changes those configurations from there, then it will affect the entire device fleet whenever the app is installed. If someone needs additional configurations for a specific device/group of devices, they can configure them through the policy.

Actions #3

Updated by Oshani Silva 9 months ago

  • Project changed from product-uem 6.0.0 GA to product-uem 6.1.0 GA
Actions #4

Updated by Viranga Gunarathna 8 months ago

  • Project changed from product-uem 6.1.0 GA to Backlog
Actions #5

Updated by Arshana Atapattu 8 months ago

  • Project changed from Backlog to product-uem 6.1.0 GA
  • Type set to Platform
Actions #6

Updated by Arshana Atapattu 8 months ago

  • Project changed from product-uem 6.1.0 GA to Backlog
Actions #7

Updated by Arshana Atapattu 3 months ago

  • Description updated (diff)
Actions

Also available in: Atom PDF