App distribution is no longer a single decision. Five years ago, "put it on the App Store" was the answer to nearly every distribution question. In 2026, the landscape has fragmented. The EU Digital Markets Act has opened iOS to alternative marketplaces. Apple is actively phasing out its Enterprise Program in favor of Apple Business Manager. Progressive Web Apps have matured enough that enterprise adoption is growing 40% year over year. Microsoft retired App Center in 2025, forcing teams to rethink their beta distribution tooling. And MDM-driven deployment has become the standard for any organization managing a device fleet.
Most distribution guides go deep on a single platform. This one covers the full landscape across iOS, Android, and the web, focused on the strategic question: which channel fits your use case? This is a decision guide, not a step-by-step submission tutorial. We assume you know how to build an app. The question is where it should live.
The Distribution Channels
Public App Stores (Apple App Store, Google Play)
The default for any consumer-facing app. Public app stores give you discoverability, built-in payment processing, automatic updates, and the trust that comes with a reviewed and signed application. Over two billion active Apple devices and roughly three billion Android devices are reachable through these stores.
The trade-offs are well known. Apple and Google both take a 15-30% commission on digital goods and services (15% for developers earning under $1 million annually through the App Store Small Business Program and Google's equivalent). Apple's review process averages 24-48 hours, with Apple reporting that 90% of submissions are reviewed within that window. Google Play reviews are typically faster, often completing in hours. Both stores impose content and design guidelines that constrain what you can ship and how quickly you can iterate.
Best for: Consumer apps, SaaS products with a broad audience, and any app where discoverability and user trust matter.
Unlisted Apps (Apple App Store, Google Play)
An unlisted app lives on the store infrastructure, goes through the standard review process, and receives automatic updates, but it does not appear in search results, category listings, or charts. The only way to find and download it is through a direct link that you control.
On Apple's side, you must submit a separate request with a justification for why unlisted distribution is necessary. Approval is not guaranteed. Google Play supports unlisted distribution more straightforwardly through its console settings.
One important nuance: "unlisted" means hidden, not private. Anyone who obtains the link can download the app. If you need actual access control, you need to build it into the app itself, typically through a login screen or invitation code.
Best for: Client-facing apps, partner tools, and limited-audience products that still want the credibility and update infrastructure of the app stores. Also strong for BYOD scenarios where you cannot require MDM enrollment.
Custom and Private Apps (Apple Business Manager, Managed Google Play)
Custom App distribution is Apple's framework for privately distributing applications to specific organizations. The developer publishes the app through App Store Connect, targeting it to specific organization IDs. The app goes through full App Review but never appears on the public store. The receiving organization accesses it through Apple Business Manager (ABM) and can silently deploy it to managed devices via MDM.
On Android, Managed Google Play lets organizations curate a private app catalog. Private apps can be published in minutes through Google's Custom App Publishing API, with a faster verification process than the public store. Organizations distribute them to employee devices through their EMM solution.
The main friction is on the receiving end. The client organization must have ABM or Android Enterprise configured, which can be a hurdle for smaller partners or organizations without dedicated IT staff. This is Apple's recommended path for enterprise distribution, and it is explicitly positioned as the replacement for the legacy Enterprise Program.
Best for: B2B apps built for a specific client, internal employee tools deployed to managed devices, any scenario where you need organizational-level access control.
Apple Developer Enterprise Program (Legacy)
The Enterprise Program costs $299 per year, requires 100 or more employees, and puts you through a rigorous application process that Apple is actively discouraging most organizations from pursuing. Its one advantage is that apps bypass App Review entirely, which allows for instant deployment of updates. The downsides are significant: enterprise distribution certificates expire annually (and all installed apps stop working if you miss the renewal), you are responsible for hosting and distributing the app yourself, and Apple closely monitors for abuse of the "internal employees only" restriction.
For any new project starting today, the Enterprise Program should not be your first consideration. The combination of Custom Apps for managed devices and Unlisted Apps for unmanaged devices covers nearly every private distribution use case at a fraction of the cost and complexity. If you are currently on the Enterprise Program, Apple provides a migration path to the standard program, though it requires republishing your app with a new Bundle ID.
EU Alternative Marketplaces (Digital Markets Act)
The EU's Digital Markets Act required Apple to support alternative app distribution starting with iOS 17.4. As of mid-2025, EU users can install apps from third-party marketplaces, and developers can distribute iOS apps outside the App Store for the first time. Epic Games, AltStore, and others have launched storefronts. Apple charges a Core Technology Fee that is transitioning to a Core Technology Commission on digital goods and services by January 2026.
This only applies in the 27 EU member states. The economics are still settling, and user adoption of alternative marketplaces remains early. Most developers we talk to are watching rather than jumping. If you are building specifically for a European audience and the commission structure matters to your margins, this channel is worth evaluating. For everyone else, it is worth understanding but not worth building a distribution strategy around yet.
TestFlight and Google Play Testing Tracks
These are beta and pre-release distribution channels, not long-term distribution solutions. TestFlight supports up to 10,000 external testers with 90-day build expiration. The first build of each new version requires Apple review; subsequent builds with the same version number typically auto-approve. Google Play offers internal, closed, and open testing tracks, with closed tracks capable of targeting specific organizations through Managed Google Play.
One timing note: Microsoft retired Visual Studio App Center in 2025, which was a popular cross-platform beta distribution tool. Teams that relied on it have migrated to TestFlight, Google Play tracks, Firebase App Distribution, or third-party alternatives like Appcircle. If your team has not completed that migration, prioritize it.
MDM and EMM Distribution
Mobile Device Management solutions like Jamf, Microsoft Intune, Scalefusion, and IBM MaaS360 push apps directly to managed device fleets. On Android with a fully managed device profile, apps can be installed without any app store involvement. On iOS, MDM distribution still routes through Apple Business Manager for most use cases, but the installation itself is silent and requires no action from the end user.
MDM is not a developer tool. It is an IT operations tool. But developers need to understand it because it dictates how the app gets packaged, signed, and configured. If your app will be deployed to corporate-owned devices, kiosks, or field equipment, you are building for an MDM-managed environment whether you planned to or not.
Best for: Corporate device fleets, kiosk deployments, field worker devices, any scenario where IT needs to control what is installed and enforce updates.
Progressive Web Apps (PWAs)
PWAs bypass app stores entirely. You distribute via a URL, a QR code, or a link in an email. Users "install" the app by adding it to their home screen from the browser. There is no submission process, no review, and no commission.
On Android, PWA support is strong. You can even publish a PWA to Google Play using Trusted Web Activity, which wraps your web app in a native shell. On iOS, PWA capabilities remain limited by Apple's requirement that all browsers use the WebKit engine. This means no background sync, limited push notification support, and no App Store distribution. The EU's DMA pressure has not materially changed this in practice as of early 2026.
Enterprise PWA adoption is growing. A TechCrunch Q1 2025 brief reported that 55% of enterprise mobility leaders planned to invest in hybrid approaches incorporating PWAs. The trade-off is user trust: an Accenture study from mid-2025 found that 30% of users expressed less trust in apps installed from a browser compared to an official app store.
Best for: Content-heavy apps, budget-constrained teams, emerging markets with low bandwidth, internal tools where app store overhead is not justified.
Direct Sideloading (APK/IPA)
Android allows direct installation of APK files with a user opt-in setting. This is common for internal QA, proof-of-concept demos, and distribution in markets where Google Play is unavailable or restricted. On iOS, direct sideloading is not available outside the EU's alternative marketplace framework and the Enterprise Program.
Sideloading carries real risk. There is no store review, no automatic update mechanism, and no malware scanning beyond what the device OS provides. We do not recommend it as a production distribution strategy. Use it for internal testing only, and migrate to a managed channel before you ship to real users.
Choosing the Right Channel
The right distribution channel depends on three questions: who are your users, are their devices managed, and where are they located? The following table maps common scenarios to recommended channels.
| Use Case | Primary Channel | Secondary Option | Notes |
|---|---|---|---|
| Public consumer app | App Store + Google Play | PWA for additional reach | Invest in ASO. This is a marketing channel, not just a distribution channel. |
| B2B client-facing app | Unlisted App Store | Custom Apps if client has ABM/Android Enterprise | "Hidden" is not "private." Build access control into the app. |
| Internal tool (managed devices) | Custom Apps via ABM/Managed Play + MDM | MDM-only on Android (fully managed) | Apple's recommended enterprise path. Coordinate with the client's IT team. |
| Internal tool (BYOD/unmanaged) | Unlisted App Store | PWA | You cannot require MDM on personal devices. Unlisted gives store credibility without store visibility. |
| Beta/QA testing | TestFlight + Google Play closed track | Firebase App Distribution | App Center is gone. Migrate if you have not already. |
| EU-specific distribution | App Store (with DMA awareness) | Alternative marketplace | Economics are still settling. Evaluate the CTC structure before committing. |
| Kiosk or field device | MDM/EMM | Custom Apps (Android: direct APK via fully managed profile) | IT owns the deployment. Developers own the packaging and signing. |
| Budget-constrained or content-heavy | PWA | Unlisted App Store | Strong on Android. Limited on iOS. Test push notification behavior on both platforms. |
Distribution Channel Comparison
For a quick reference across all channels, use this comparison. The table covers the key decision factors: whether the channel requires a store review, whether the app is publicly discoverable, update behavior, platform support, and cost.
| Channel | Store Review | Discoverable | Auto Updates | iOS | Android | Cost |
|---|---|---|---|---|---|---|
| Public App Store | Yes | Yes | Yes | Yes | Yes | $99/yr (Apple) + 15-30% commission |
| Unlisted | Yes | No | Yes | Yes | Yes | $99/yr (Apple), $25 one-time (Google) |
| Custom/Private | Yes (Apple), Faster (Google) | No | Yes (via MDM) | Yes (ABM) | Yes (Managed Play) | $99/yr (Apple), $25 one-time (Google) |
| Enterprise Program | No | No | Self-managed | Yes | N/A | $299/yr, restricted access |
| EU Marketplaces | Varies by store | Within marketplace | Varies | EU only | N/A | CTC on digital goods |
| TestFlight/Play Tracks | First build (Apple) | No | Yes (within beta) | Yes | Yes | Included with dev account |
| MDM/EMM | No (Android), Via ABM (iOS) | No | IT-controlled | Via ABM | Yes | MDM licensing (varies) |
| PWA | No | Via web search | Instant (web deploy) | Limited | Yes | Hosting only |
| Direct Sideloading | No | No | No | EU/ADEP only | Yes (user opt-in) | Free |
What Is Changing
Several trends are reshaping how apps get distributed, and they should inform your planning even if they do not affect your current project.
The EU DMA is fragmenting iOS distribution. Alternative marketplaces exist, but adoption is slow and the fee structure is still in flux. Apple's transition from the Core Technology Fee to the Core Technology Commission by January 2026 adds uncertainty for developers evaluating the economics. This is worth monitoring if you serve European users, but for most teams it is not yet worth building a distribution strategy around.
Apple is phasing out the Enterprise Program. Custom Apps via Apple Business Manager are the clear replacement. Apple's own documentation steers applicants away from the Enterprise Program and toward the standard $99 developer account. If your organization is still distributing through an enterprise certificate, plan your migration now. The combination of Custom Apps and Unlisted Apps covers nearly every scenario the Enterprise Program was used for.
PWAs are closing the gap on Android but stalling on iOS. Enterprise adoption is growing, and Android treats PWAs as capable applications with broad API access. On iOS, Apple's WebKit requirement means PWA capabilities are entirely at Apple's discretion. Despite EU regulatory pressure and a €500 million fine in early 2025, nothing has materially changed for iOS PWA functionality. If your audience is cross-platform, plan for an asymmetric experience.
App Center is gone. Microsoft retired Visual Studio App Center in 2025. Teams that relied on it for beta distribution have scattered across TestFlight, Firebase App Distribution, Appcircle, and other tools. If you have not completed your migration, this is overdue.
Multi-channel distribution demands automation. When you are shipping to a public store, a testing track, and an MDM catalog simultaneously, manual processes do not scale. Tools like Fastlane, the Google Play Publishing API, and the App Store Connect API make multi-channel pipelines manageable. If you are distributing through more than one channel, invest in CI/CD automation early.
Frequently Asked Questions
Yes, and most apps should. A typical lifecycle might start with TestFlight and Google Play closed tracks for beta testing, move to an unlisted listing for early client access, and eventually land on the public stores for general availability. Enterprise apps often live on Custom Apps via ABM and Managed Google Play while also being pushed through MDM. The key is that each channel may require different signing configurations and provisioning profiles, so plan your build pipeline accordingly.
The critical distinction is whether the end user's device is managed by an organization's IT department. Custom Apps require the receiving organization to have Apple Business Manager set up and typically deploy through MDM. Unlisted Apps do not require any organizational infrastructure. Users download them from the App Store using a direct link, just like a public app. If your audience includes contractors, partners, or employees on personal devices, Unlisted is usually the right choice.
It depends on what your app needs to do and where your users are. If your app is content-heavy, does not require deep hardware access, and needs to reach users quickly without app store friction, a PWA is a strong choice, especially on Android. If you need reliable push notifications on iOS, background processing, access to Bluetooth or NFC, or the trust signal of an app store listing, native is still the better path. Many teams are adopting a hybrid approach: a PWA for broad web reach and a native app for users who need the full experience.
The DMA's alternative marketplace provisions primarily affect iOS, because Android has always allowed sideloading and third-party app stores. Google Play is the dominant Android store, but users can install apps from Amazon Appstore, Samsung Galaxy Store, F-Droid, and direct APK downloads without regulatory intervention. The DMA's impact on Android is more about payment processing and interoperability than distribution channels.
If you are planning a mobile app and need help choosing the right distribution strategy for your audience, we can help. Learn more about our mobile development services or get in touch to talk about your project.
