New Google and Apple policies are changing the economics of app distribution. Alternative payments are only part of it. This introduces a case for adding a third distribution channel: what changed, what it takes to stand one up, and how to test it without betting the roadmap.
Rulings, settlements, and new laws in the US, EU, UK, Japan, Korea, and Australia have changed how Google and Apple charge developers. Both companies have redesigned their fee structures to maintain an economic relationship with transactions that originate in their ecosystems. That’s why adding DTC checkout to a store app doesn’t reduce fees as much as it previously did.
For most developers, this is not an argument for abandoning Google Play or the App Store. It is about adding another distribution channel alongside them.
A store-distributed app can use alternative billing or external web payments and stay tied to the store's economics.
With an off-store app, the developer takes ownership of the install path, payments, updates, and ongoing customer relationship.
Google and Apple are giving developers more flexibility in how payments are processed, but both can still charge fees on transactions tied to their ecosystems.
The platforms differ most clearly once distribution moves outside the store:
That difference makes Android the more straightforward starting point for off-store distribution, and shifts the bigger decision from payment method to distribution.
EEA, UK, and US move to Google's new service fees and the 5% Play billing fee.
Australia and Japan move to the new fee structure. Apps Experience and Games Level Up rate cards become available. Android developer verification requirements begin in Brazil, Indonesia, Singapore, and Thailand.
Apple's EU business terms take effect, including the 5% Core Technology Commission.
South Korea moves to the new fee structure and programs.
Google's fee structure reaches the rest of the world.
From June 30, 2026, Google separated its Play service fee from its billing fee in the US, UK, and EEA. Other regions follow through Sept. 30, 2027.
The service fee applies whether a transaction uses Google Play Billing, alternative billing, or an external web link. The separate Play billing fee applies only when Google Play processes the payment.
For one-off purchases, existing installs can carry higher fees than new installs. Auto-renewing subscriptions are 10% either way.Transactions completed within 24 hours of following an external web link follow the rates above, with one exception: non-recurring purchases from existing installs are charged 20% at the standard rate, or 15% on the Apps Experience and Games Level Up programs.Alternative payment methods can also add operational requirements. In applicable markets, developers may need to offer Google Play Billing alongside another payment option, follow Google's UX rules, handle support and refunds, and report authorized transactions.
From Oct. 1, 2026, Apple’s new EU business terms take effect. The initial acquisition fee and store services fee are eliminated, while Apple introduces a 5% Core Technology Commission on digital transactions in apps distributed outside the App Store.
EU only. Reduced rates apply to developers in the App Store Small Business Program, Mini Apps Partner Program, or Video Partner Program.
Apple also retains Notarization requirements for apps distributed outside the App Store, along with requirements around payment choice, parental controls, and link-outs.
Creating the APK is one part of the equation. Going off-store means taking responsibility for distribution, installation, updates, measurement, and other functions the app store normally handles. An off-store strategy has to solve four core problems:
Your distribution model determines how the app reaches the user. Your payment model determines how transactions are processed. The two decisions are connected.
Google Play fees vary by region, developer size, program eligibility, and transaction type. Confirm current rates before modeling any distribution strategy.
In a store-distributed app, DTC payments are an alternative to store billing. The store still controls distribution, and store fees may still apply to subsequent transactions.
In a dedicated off-store app, DTC payments are built into the experience from the start.
The developer controls the acquisition path, payment experience, customer relationship, and revenue flow.
Common providers include Xsolla, Appcharge, Stash, Stripe, and Adyen. Compare them based on revenue share, Merchant of Record support, supported payment methods, geographic coverage, product capabilities, and integration effort.
Across its global footprint, DT provides the direct-to-device infrastructure for distributing, installing, updating, and growing Android apps outside app stores.
DT enables the distribution layer, while the developer maintains control of the app, payments, and customer relationship.
Your distribution model determines how the app reaches the user. Your payment model determines how transactions are processed. The two decisions are connected.
DT delivers APKs directly to Android devices through preloads across its OEM and telco footprint, which spans more than one billion devices. No store listing required.
SingleTap installs apps without a store handoff. Developers can use SingleTap links for lighter integrations or the SDK for deeper control, with installs triggered from websites, banners, UA campaigns, or app-to-app journeys on Android.
SingleTap can also deliver direct-to-device updates, so removing Google Play from distribution doesn't strand users on old builds. Off-store, app management moves to you rather than the store.
Run UA campaigns that install the app directly powered by SingleTap with no store handoff. App Agent surfaces off-store apps for organic discovery on supported devices, and takes no cut of your app revenue.
Payments remain with your chosen DTC provider, while the app and customer relationship remain with you.
Off-store does not have to replace your store strategy.
Pick an app weighted toward in-app purchases, where the fee gap is widest, and one whose users you already understand. Subscription revenue is 10% on Play either way. A new title makes it hard to separate channel results from product results.
Run the off-store version at feature parity with your store app. An under-invested build produces a misleading read, and the channel gets written off on bad data rather than real results.
Run identical acquisition mechanics down both paths, so the only variable is what happens after the click.
Measure acquisition cost, retention, and long-term user value across both, then expand what performs.
Before launch, audit any part of your Android stack that assumes a legitimate install must come from Google Play.
DT recommends completing validation at least two weeks out.
New-user onboarding works
Returning-user login and authentication work
Guest-account creation works
Cloud saves and live-ops events work
Push notifications work
Payment and subscription flows work
Merchant of Record impact is reviewed
In-app purchases and monetization are verified
Install and upgrade paths work
Crash reporting and analytics are verified
Backend entitlement checks pass
Changing the checkout still means paying the store. Changing the distribution doesn't. On Play, a one-off purchase from an existing install costs 25%, while off-store, no Play fee applies.
Tell us what you are distributing and where, and DT can walk through what an off-store build would require.