Forum Discussion
Android Developer Verification Requirements in AE
I would love for the same blanket exception that was applied to GPP to also be applied in this circumstance for apps installed on Fully Managed devices by a Device Owner DPC. In that situation an enterprise admin is electing to install a business app on assets owned by the same enterprise they do not need or want Google sitting in the middle of that dictating what they are or are not allowed to install on their own devices.
Agreed - and we were able to get an exemption for apps installed by a DPC. Lizzie's linked to the full post below.
mattdermody jasonbayton I'm keen to understand if anything falls outside these exemptions. Are you aware of any examples where companies install apps onto their device though other side-loading methods (i.e. without their EMM's DPC involved)? If so - why?
Thanks in advance for your feedback. Feel free to contact Lizzie to coordinate a 1:1 call if that's easier.
Yes, there's a lot of APK sideloading particularly with smaller companies using AMAPI as we can't still distribute via the EMM platform. I've also seen very rare instances of companies building their own app catalogue app/webapp as a front-end to pull down APKs.
One other consideration is apps that self-update via a remote repo. Presumably if an app is installed, any update to the package is automatically permitted?
E: Sorry I was thinking of policy-allowlisting and replacement of one package with another using the same pname. This may fix that too in current state, but allowing sideloading here would undo that.
