App Distribution
- Distribution of an enterprise app - decision-making basis
- Distribution via public app stores
- Distribution via Apple App Store - Advantages
- Distribution via Apple App Store - disadvantages
- Distribution via Google Play Store - advantages
- Distribution via Google Play Store - disadvantages
- Distribution via beta programs of the public app stores
- Distribution via Apple Testflight - Advantages
- Distribution via Apple Testflight - Disadvantages
- Distribution via Google Alpha and Beta Testing - Advantages
- Distribution via Google Alpha and Beta Testing - Disadvantages
- Distribution via internal enterprise app store
- Distribution of iOS apps via Enterprise App Store - advantages
- Distribution of iOS apps via enterprise app store - disadvantages
- Distribution of Android Apps via Enterprise App Store - Advantages
- Distribution of Android apps via enterprise app store - disadvantages
On this page
- Distribution of an enterprise app - decision-making basis
- Distribution via public app stores
- Distribution via Apple App Store - Advantages
- Distribution via Apple App Store - disadvantages
- Distribution via Google Play Store - advantages
- Distribution via Google Play Store - disadvantages
- Distribution via beta programs of the public app stores
- Distribution via Apple Testflight - Advantages
- Distribution via Apple Testflight - Disadvantages
- Distribution via Google Alpha and Beta Testing - Advantages
- Distribution via Google Alpha and Beta Testing - Disadvantages
- Distribution via internal enterprise app store
- Distribution of iOS apps via Enterprise App Store - advantages
- Distribution of iOS apps via enterprise app store - disadvantages
- Distribution of Android Apps via Enterprise App Store - Advantages
- Distribution of Android apps via enterprise app store - disadvantages
Distribution of an enterprise app - decision-making basis
Background information
Companies are increasingly deciding to support certain work processes with a mobile app. Among many other conceptual issues, the question of how to distribute this app to users quickly arises. Often, the use case is that not only employees, but also external people should get the app - this can include service providers, partners or customers, for example. In most cases, this app is also explicitly not intended for a broad customer base, but is aimed at selected professional users. The following sections in this Insight should help you decide on the best distribution method.
Distribution via public app stores
Apple and Google each provide an infrastructure for distributing apps. For Apple, apps are made available to end users through the Apple App Store. Every iOS device has the App Store app pre-installed.
Apps are managed and published via the developer portal and the iTunesConnect portal. On Google, apps are made available to end users via the Play Store. The Play Store app is preinstalled on every Android device.
The administration and publication of apps for this is done via the developer portal. Apple and Google define the framework for publishing apps via their systems.
If a device is managed via an MDM system, the Store app can also be locked for the user and may therefore not be available to the end user.
Distribution via Apple App Store - Advantages
- Apps are available to end users via Apple’s standard mechanism
- Apps do not need to be re-signed and re-provisioned with an updated provisioning profile after one year.
- Apps can be selectively enabled or blocked for individual countries, if necessary.
- Apps can be offered for a fee - if desired - in defined structures (Apple charges a percentage commission fee of 15% for this)
- Apple provides the infrastructure for distribution and billing
Distribution via Apple App Store - disadvantages
- Users need an Apple ID on the end devices to install apps from the Apple App Store
- For enterprise customers with managed devices, the Apple App Store may be blocked via MDM
- All Apple specifications must be met, such as support for new device classes like iPhone X
- In a review, Apple reserves the right not to publish the app or to subsequently remove it.
- The review can lead to delays of up to 10 days (currently, the average review duration is about 3 working days).
- Apps can only be made available to selected user groups on a very limited basis
Distribution via Google Play Store - advantages
- Apps are available to end users via Google’s standard mechanism
- Apps can - if necessary - be selectively enabled or blocked for individual countries
- Apps can - if desired - be offered for a fee in defined structures (Google charges a percentage commission fee of 15% for this)
- Google provides the infrastructure for distribution and billing
Distribution via Google Play Store - disadvantages
- Users need a Google account to install apps from the Play Store
- For enterprise customers with managed devices, the Play Store may be locked down via MDM
- All Google requirements must be met - such as the Cordova version.
- After automated app scans, Google reserves the right to remove the app from the store at a later date.
- Due to technical scans, the release of apps can be delayed by a few hours
- Apps can only be made available to selected user groups to a very limited extent
Distribution via beta programs of the public app stores
Apple and Google each offer a beta testing program in addition to the distribution of public apps. At Apple, apps are made available for beta testing to end users via the TestFlight app. On iOS devices, this app can be post-installed from the Apple Store app.
The administration and publication of apps for this is done via the Developer Portal and the iTunesConnect portal in the TestFlight area. On Google, apps are made available for alpha or beta testing via the Play Store. The Play Store is preinstalled on every Android device.
The administration and publication of apps for this is done via the Developer Portal in the Alpha and Beta Testing area. Apple and Google define the framework for publishing apps via their systems.
Distribution via Apple Testflight - Advantages
- Apps are available to users via a mechanism provided by Apple
- Apps can be selectively released to individual users
- Apple provides the infrastructure for distribution and billing
Distribution via Apple Testflight - Disadvantages
- Users need an Apple ID to install apps from the Apple App Store
- One-time installation of the TestFlight app is required to install the app
- Apple reserves the right not to publish the app in a “reduced” review
- Delays of up to 10 days may occur due to the review (currently, the average review duration is about two working days).
- App signature expires after 90 days
The TestFlight service is primarily intended for a short testing period before publishing an iOS app. It is not suitable for permanent operation due to the short validity of the signature.
Distribution via Google Alpha and Beta Testing - Advantages
- Apps are available to users via a mechanism provided by Google
- Apps can be selectively enabled for individual users
- Google provides the infrastructure for distribution and billing
Distribution via Google Alpha and Beta Testing - Disadvantages
- Users need a Google ID to install apps from the Play Store
- For enterprise customers with managed devices, the Play Store may be locked down via MDM
Distribution via internal enterprise app store
In addition to distributing apps via the respective public stores, Apple and Google also offer mechanisms for distributing apps internally, primarily for enterprises. In the case of Apple, the Apple Enterprise program and an enterprise app store such as Relution are required as prerequisites.
The apps are made available to end users via a separate App Store app or a mobile website. Apps are managed via the developer portal.
Apps are distributed via the respective enterprise app store provider. At Google, apps can be made available for download and installation via a web service.
For special devices, such as Samsung, optimized installation and distribution mechanisms can be used. Apple and Google define the options for distributing apps in parallel with their systems.
Distribution of iOS apps via Enterprise App Store - advantages
- Apps can be distributed to selected user groups, e.g. as a deep link or after logging in with previously configured user names and passwords
- Users do not need an Apple ID to install apps from an internal Enterprise App Store
- Not all Apple requirements have to be met
- The release of app updates is not delayed by a review from Apple
- Some enterprise app stores (e.g. Relution) can be used without device management (MDM)
- An existing user management system (ActiveDirectory/LDAP) can be connected so that users do not need new credentials
Distribution of iOS apps via enterprise app store - disadvantages
- Apps are available to end users via a special mechanism that is approved by Apple, but requires initial configuration by the user (see here)
- Apps must be re-signed and re-provisioned with an updated Provisioning Profile after one year. However, this can be automated with Relution, so there is actually no disadvantage here.
- The infrastructure for distribution can be provided as a cloud service or on-premise, for example.
- According to Apple’s guidelines, apps may only be distributed to employees, interested parties and partners, but above all to a known group of users.
Distribution of Android Apps via Enterprise App Store - Advantages
- Apps can be distributed to selected user groups, e.g. as a deep link or after logging in with previously configured user name and password
- Users do not need a Google ID to install apps from an internal enterprise app store
- Not all Google requirements have to be met
- Release of app updates is not delayed by Google technical scans
- Some enterprise app stores (e.g. Relution) can be used without device management (MDM)
- An existing user management system (ActiveDirectory/LDAP) can be connected so that users do not need new credentials.
Distribution of Android apps via enterprise app store - disadvantages
- Apps are available to end users via a special mechanism that is approved by Google, but requires initial configuration by the user
- The infrastructure for distribution must be provided, for example, as a cloud service