PRODUCT IOTS » Backlog

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.