Before you set up your branded app, decide how Salesforce manages the release process and who your app is available to. These two decisions (your distribution method and your distribution type) shape every step of your setup.
Setting up distribution involves two choices that you make before you begin:
- Distribution method: Whether Salesforce handles the entire process, you manage key steps yourself, or Salesforce delivers the app binary for you to sign and submit.
- Distribution type: Whether your app is publicly available on the Apple App Store or Google Play, or privately distributed only to users within your organization.
Step 1: Select a Distribution Method
Your distribution method determines how much of the build, signing, and submission process Salesforce handles on your behalf. Select based on your organization's familiarity with the app stores and how much control you want over releases.
Binary Handoff Distribution Method
If you choose Binary Handoff, Salesforce builds the application binary file (.ipa for iOS or .aab for Android) and delivers it directly to you. Your organization is then responsible for re-signing the binary with your own signing certificates and submitting the app to the Apple App Store and/or Google Play Store. This method provides the maximum level of control over the final app signing and submission process. It’s ideal for orgs with specific security protocols or established internal processes for distributing mobile applications that require them to handle the final signing and upload to the app stores themselves.
Binary Upload Distribution Method
If you choose Binary Upload, you’re responsible for submitting App Store listing information, submitting the app for review, and releasing the app to your users. After you invite Salesforce to your App Store’s accounts and grant access to the credentials, Salesforce uploads the app to your account. Salesforce then manages your app branding assets and app updates.
This distribution method is ideal for orgs who already have apps in the app stores and are familiar with how the app stores work. You can take advantage of App Store features like staged releases.
Fully Managed Distribution Method
If you choose Fully Managed, Salesforce builds and uploads your app to your App Store’s accounts after you grant access to the credentials. Salesforce then manages your App Store listing information, app branding assets, app updates, and releasing the app to your users.
This distribution method is ideal for orgs that aren’t familiar with the app stores and its complexities.
| Distribution Feature | Fully Managed | Binary Upload | Binary Handoff |
| Best For | Organizations not familiar with the app stores that prefer Salesforce to handle the entire process. | Organizations familiar with the app stores that want flexibility and control over their app's store listing, release schedule, and testing of new versions. | Organizations with in-house Apple and Google expertise, specific security protocols requiring internal code signing, or established processes for manual app submission and prior mobile app management. |
| App Build | Salesforce builds the app binary. | Salesforce builds the app binary. | Salesforce builds the app binary (.ipa or .aab) and delivers it to you. |
| Code Signing | Salesforce handles all code signing. | Salesforce handles all code signing. | You have full control. Your organization re-signs the app binary with your own distribution certificates and private keys. |
| App Store Listing & Metadata | Salesforce manages all store listing information (screenshots, descriptions, etc.). | Salesforce manages all store listing information (descriptions, etc.). | You have full control. You submit and manage all store listing information. |
| Upload to App Stores | Salesforce uploads the signed app binary to the store. | Salesforce uploads the signed app binary to your store account. | You have full control. Your organization is responsible for uploading the re-signed binary to the app stores. |
| Submission for Review | Salesforce submits the app for final review and handles the release lifecycle. | You have full control. You're responsible for submitting the app for review. | You have full control. You're responsible for submitting the app for review. |
| Release Management | Salesforce manages the release to your users after Apple or Google approval. | You have full control. Use advanced app store features like choosing your own release schedule and performing staged rollouts. | You have maximum control over the entire submission and release process. |
Step 2: Choose a Distribution Type
If you choose Fully Managed or Binary Upload, you also choose a distribution type: public or private. Your distribution type determines who can find and install your branded app.
- Public distribution: Your app is listed on the public Apple App Store or Google Play Store. Any user can search for and download it.
- Private distribution: Your app is available only to users within your organization. On iOS, distribution is managed through Apple Business Manager (ABM). On Android, it's managed through Managed Google Play.
The following table summarizes the account and access requirements for each combination of platform and distribution type when using the Fully Managed or Binary Upload distribution methods.
| Platform | Private Distribution | Public Distribution |
|---|---|---|
| Android |
|
|
| iOS |
|
|
iOS Distribution Guidelines
Apple's distribution policies strictly define which distribution type you must use based on your app's audience:
- Business to Consumer (B2C) apps must use public distribution on the public App Store.
- Business to Business (B2B) and Business to Employee (B2E) apps must use private distribution through Apple Business Manager (ABM).
- You need a separate Apple Business Manager (ABM) ID for each country where you want to privately distribute your app. For example, distributing in India requires a valid ABM ID for India.
- If you change the distribution type for an existing live app, you can't reuse the same app name. For example, switching a live app from private to public distribution requires a new app name. See the App Store guidelines for more information.
Android Distribution Guidelines
Google Play offers more flexibility than Apple in matching distribution type to audience:
- B2C, B2B, and B2E apps can use either public or private distribution based on your use case.
- You can switch an existing app between distribution channels — from private to public or from public to private — at any time.
- For private distribution, you must use a G-Suite account with your organization's domain. App access is limited to users in that G-Suite organization. For example, if your organization is AYZ Inc., use a G-Suite tied to that domain. Your Google Play Store admin can review Google's Mobile Device Management (MDM) and Enterprise Mobility Management (EMM) documentation, or contact your EMM provider for details.
- There's no beta app for Android private distribution. If you don't use G-Suite and Google for Work, see Distribute private apps in Google Play Help.
- Advantages of Binary Upload and Binary Handoff Distribution Methods
If your org is familiar with how the app stores work, the Binary Upload and Binary Handoff Distribution Methods have many advantages for managing the release of your app on your end.