Private Managed Google Play vs Enterprise App Deployment

AW
Adam Williams
Panasonic Manufacturing UK Ltd - CPE

Assuming Managed Google play has already been assigned to MC and some applications from the wider public google play are present in an app policy.

In the case where we have private applications, does anyone have an opinions/best practise/know of difference/limitations between deploying these applications via Enterprise App deployment vs Adding them as a Private application to Managed google play.

Thanks in advance

Adam

3 years ago
Android
ANSWERS
RS
Rafael Schäfer
3 years ago

The difference is for example:

If you deploy it via Enterprise App, you can use every apk, even this is available in playstore already but if you try to upload an apk in the private playstore there's a validation of google and it's package name has to be different from those already in the playstore.

You also can't delete apps uploaded to the private playstore yourself, you have to follow a procedure and ask google to remove it.

Also you could provide apps uploaded to the private playstore to the entire playstore users or defined users (via Mail).

If deployed via Enterprise Apps, the app is not displayed in the playstore on the device but in the app catalogue (In House) in the mobicontrol app.

So, I think it's more vor developers and/or app distributors.

I'm not sure if there are other (enrollment related) differencies but i would prefer if you enroll an apk to use the Android Enterprise apps (please read following before: https://discussions.soti.net/thread/stop-an-app-from-updating) or a Profile (which is at least the savest way but there's no possibility for managed app config).

AW
Adam Williams
3 years ago

Really appreciate that info Rafael, the point about deleting and a package already existing in public playstore is really useful.

For the verification on the package name and the need to ask google to delete it from the private store. Does that mean, in general, one should ask the developers permission to upload to the private store? Or is this not necessary as multiple copies of this package will be installed in numerous private accounts? 

Potentially one other (minor) difference I have seen is applications installed from managed google play (but only tested for public apps rather than private) is the applications will add to the (2nd) homescreen automatically if the launcher setting is setup this way. however, enterprise applications do not seem to appear on the homescreen even then this setting is activated in the launcher.

Thanks

Adam

RS
Rafael Schäfer
3 years ago

Regarding your first question, i think it's not possible to upload apps with the same package name to any private account, only possilbe if you use profile deployment or Enterprise app deployment. We had some trouble before exactly because of that. 

So in that case you would have to ask the developers to build a package exactly for your company and (for example) extend the existing package name in the new apk file with your company name. But thats effort on developer side and would be needed for every customer of the developers, so normally declined. In general every package name known by the playstore must be unique and be aware that the check is case sensitive.

Yes, you are right regarding the link on homescreen, same for deploying via profile (no link created on homescreen).