2

My goal is to distribute different release versions of the same app to different enterprise customers (based on business licensing). i.e. Different customers have paid for version X or Y of our one app, and we need to be able to install those different versions of the app at different customers, if they buy new devices, for example.

SO posts like this and this are actually about graphics resource delivery or file size.

This post is close, but essentially deals with different app resources for the same app version, rather than different app versions for different people.

There are delivery options such as sending an APK via email or hosting the APK on a company website, but these require customers to enable trusting unknown sources, which cheapens the experience.

The Google delivery options include:

  1. Google Play Public apps
  2. Private apps via Google Play (here and here), including their Enterprise Mobility Management (EMM)
  3. This option also describes publishing internal apps for another organization

Option 1 would require a different package name per version, and wouldn't allow for upgrades.

Option 2 Seems to suggest that you can only deploy to users in your G-Suite

Option 3 Seems to require that the target customer uses G-suite for their mobile management, and then making any bug fixes to a particular released version would require updating each target customer's private enterprise app.

None of these options is attractive. Is there another option that I've missed?

Mike T
  • 4,747
  • 4
  • 32
  • 52
  • What not only one version but with a log in system? Each user is linked to a paid version and, based on that, he has only access to the specifics parts/options of the app? – Eselfar Jul 12 '17 at 08:21
  • The servers are typically hosted in customer VPNs, so not accessible over the general internet, and don't always have outward internet access either – Mike T Jul 12 '17 at 08:48

0 Answers0