Forum Discussion
How to manage app using Intune
Thank you for the response.
Our case is slightly different.
The vendor does not provide the apk with a different package name since they have over 1000 customers. Furthermore, every customer uses the app differently. For context, it is the manufacture and warehouse app. The customers might have different ways to do tasks. Therefore, there are customisations and adjustments to suit each customer.
Every now and then, we could have an issue with the new version. We use Intune to manage the rollout. However, if we enrol the device with Android Enterprise, we cannot upload the rollback on time using private since it has an issue with the package name.
Our devices are currently enrolled as Device Admin. However, we are concerned about Intune to stop supporting it next year.
Regards,
1 or a million customers, developers and customers will have to adapt to this alternative method of app management if relying on a platform that cannot distribute APKs.
It's an outdated and higher-risk method of app distribution in any case, so once transitioned you'll benefit from lower network usage, faster installs, and other benefits of Play.
Your struggles with version update issues can also be quelled with more intentional testing periods and app update management policies that'll allow you to install on test devices and validate before going live to your estate. This same approach can delay updates to periods when your developer is available too for more convenient version iterations.
But ultimately if it's a critical business application they need to work with you to support a custom package name and allow you to manage this end-to-end yourself. It's not difficult, nor high-effort since a bit of scripting can automate as many packages and names as they could want.
Discuss it with them.
Is it possible to share private Google Play apps between different organizations?
Process could be something like this:
- From MDM #1 Play iframe (for instance Intune) upload a private app
- Goto Advanced Editing / Google Play Console
- Under advanced settings add another organization id
- On MDM #2 it should show up as a "public" app in Play.
This is similar to what I would do with a public app that is only shared with a select organizations.
The advantage over public Play would be the less strict rules of private Play that allow older target SDKs etc.
Will this even work and if so is there something to be aware off?
Bo
Yes it is, and the process follows essentially what you just described. Though if you're in a situation needing to support multiple enterprise IDs, going through the Google Play console from the start and marking the app as private will give you all the benefits of private apps, without the burden of it being locked to one particular enterprise ID.
Marking private is under advanced settings > managed Google Play in the store listing area
