iOS App Store vs Google Play 2026: Fee, Approval, and Implementation Framework

The framing here is deliberate. Every mobile app team we work with treats the platform choice as an implementation problem. That includes industrial, NGO, and consumer contexts. However, in 2026, it is primarily a monetization and compliance problem. Implementation follows.

The 2026 commission map at a glance

Both platforms now run tiered fee structures with regional carve-outs. Furthermore, the commission you actually pay depends on four variables. First, your annual revenue tier. Second, transaction type (one-time versus subscription). Third, the user region. Finally, whether you route payments through the platform or an alternative, the table below summarises the base rates. All rates verified against Apple developer documentation and Google Play Console policy pages as of July 2026.

The headline numbers matter less than the second-order effects. Both platforms have complicated their fee schedules to satisfy regulators. As a result, the compliance overhead of choosing an alternative billing route often exceeds the fee savings. The rest of this article unpacks each row.

iOS App Store fee structure in 2026

Apple’s global commission structure has not moved. WWDC26 confirmed no changes to the standard 15/30% split. Instead, Apple’s headline updates focused on new pricing options. Notably, iOS 26.5 introduced monthly subscriptions with a 12-month commitment. Additionally, forthcoming Bundles and Suites offering types will ship later in 2026. However, no fee revisions were announced.

• Standard commission: 30% on paid apps and in-app purchases.
• Small Business Program: 15% if you earned $1 million USD or less in total proceeds in the prior calendar year and remain under that threshold in the current year. Additionally, small business developers with fewer than 2 million first-time downloads gain no-cost access to Apple Foundation Models on Private Cloud Compute — a meaningful benefit for AI-integrated apps.
• Auto-renewing subscriptions: 30% in Year 1, then 15% for subscribers who remain past the twelve-month mark.
• External-link entitlement (US, EU): Reader, video-subscriber, and select app categories may direct users to external payment channels via an actionable link. Fees still apply — see the EU section below.

For teams launching a new product in 2026, the Small Business Program is the default. It applies until Year 2 revenue actually breaches the $1M ceiling. Apple auto-enrolls eligible developers. However, developers must request and re-verify the entitlement each calendar year.

Google Play fee structure in 2026

Google Play’s structure is materially more fragmented than Apple’s in 2026. Specifically, the EEA, UK, and US have restructured their base service fee into a “service fee + billing fee” model. According to Google’s own Play Console documentation, more than 99% of developers subject to service fees qualify for a rate of 15% or less.

• Legacy markets (outside EEA / UK / US): 15% on the first $1M USD in annual revenue, 30% above that threshold, for non-subscription transactions. Auto-renewing subscriptions are 15% flat.
• EEA / UK / US non-subscription (new installs): 10% service fee + 5% billing fee. Developers enrolled in qualifying programs (Play Games Level Up or Apps Experience) pay 15% + 5% billing fee.
• EEA / UK / US non-subscription (existing installs): 25% + 5% billing fee (higher because these are legacy user cohorts).
• Auto-renewing subscriptions (EEA / UK / US): 10% + 5% billing fee on the first $1M USD in annual earnings.
• User Choice Billing (UCB): Developers who offer an alternative billing system alongside Google Play billing receive a 4-percentage-point reduction in the standard service fee. Available in over 35 eligible countries.

The takeaway for a 2026 launch team: model the fee as service-plus-billing rather than a single number. Furthermore, the Google Play service fee is a smaller share than most competitive comparisons still cite.

EU DMA changes that both platforms had to make

The Digital Markets Act (DMA) forced structural changes on both stores. Furthermore, these rules continue to evolve in 2026. Apple’s EU picture is the more complex of the two.

• Apple EU alternative business terms: Developers who sign the Alternative Terms Addendum pay a reduced App Store commission of 10% (Small Business Program and subscriptions after Year 1) or 17% on digital goods and services, regardless of payment processing system.
• Core Technology Fee (CTF): €0.50 per first annual install per year on EU installs exceeding one million per year, applied only to devices on iOS 17.4+ / iPadOS 18+ under the Alternative Terms Addendum. Developers with under €10M in global revenue receive a three-year on-ramp with zero CTF; those in the €10-50M tier pay CTF capped at €1M per year during the on-ramp.
• Core Technology Commission (CTC): Effective 26 June 2025, Apple charges a 5% CTC on sales of digital goods and services communicated and promoted via external purchase links. Apple originally announced a full transition from CTF to CTC by 1 January 2026, but as of mid-2026, the per-install CTF remains in force alongside the CTC. Confirm current status before signing.

Google Play’s EEA response is simpler in structure but consequential. Effective 4 June 2026, the Play EEA External Offers Program allows developers to redirect users to external offers via web links. Google charges a 10% ongoing service fee on auto-renewing subscriptions completed within 24 hours of the click. Additionally, it charges 20% (or 15% for developers in qualifying programs) on other in-app digital items. Finally, it charges €1.20 per install for app downloads acquired through external offers.

External payment and link-out arithmetic

External payment routes look attractive on paper. However, in practice, the arithmetic often does not favor leaving the platform billing rails. Consider the June 2025 fee stack for iOS non-Alternative-Terms EU apps using the external-purchase link entitlement. First, a 2% Initial Acquisition Fee for the first six months. Second, a 13% Store Services Fee (Tier 2, or 5% Tier 1 without full services). Third, a 5% Core Technology Commission. In total, that reaches up to 20% (or 12% on the reduced tier). Small Business Program members pay 15% (full services) or 10% (reduced tier).

Compare that to Apple’s standard 15% Small Business Program rate. Once payment processor fees, chargebacks, VAT collection, and dispute handling are counted, the external route often costs more. External payment makes economic sense for high-ARPU subscriptions above the $1M threshold. Similarly, it works for developers who already operate a customer billing stack in parallel. However, it rarely pays for a mobile-first startup.

App review timelines — the new normal

Review approval times on both stores lengthened materially in 2026. Apple’s historical 24-hour target — consistently met through 2023-2024 — no longer holds in the current benchmark. Additionally, app release submission volume rose 60% year-over-year across both stores in Q1 2026. That figure hit 80% on iOS alone. By April 2026, total volume was up 104% across both stores.

• iOS new submissions: Typically 2-5 days in 2026, with spikes of 7+ days during peak periods (WWDC week, iOS.x releases, Q4 holiday freeze).
• iOS updates: 24-72 hours in the current benchmark, down from a routine sub-24-hour turnaround in 2024.
• Google Play production access: 7 days or less in the best case; typical 3-7 days; worst case up to two weeks. Production access requires a minimum of 12 closed testers before promotion — a common cause of first-cycle rejection.
• Google Play updates on established accounts are often published within a few hours, similar to legacy behavior.

The practical consequence: build a two-week float into any launch marketing plan that requires store approval. Furthermore, in-app features tied to fixed dates need a similar buffer. Examples include Black Friday drops, election-day guides, and sporting events. Submit at least 10 business days before the on-sale date at both stores in 2026.

First-cycle rejection categories worth designing around

Rejection categories have shifted with the platform policy stack. On Apple, most rejections in 2026 still trace back to three issues. Namely, app crashes on launch, incomplete metadata, and App Store Review Guideline 4.2 (minimum functionality). Additionally, health-related features, in-app purchases, and kid-targeted content trigger longer review cycles. Consequently, these categories carry materially higher rejection risk.

On Google Play, the closed-testing rule blocks a growing share of new developer accounts. Specifically, Play requires at least 12 testers before granting production access. In 2025, Google blocked over 1.75 million apps from the Play Store. That figure was down from 2.36 million in 2024 and 2.28 million in 2023. Additionally, Google banned more than 80,000 developer accounts. Overall, the trendline is toward stricter enforcement, not looser.

Platform policy shifts are expected to land between now and Q1 2027

Both platforms have material policy changes with fixed dates in the current cycle. These changes affect the implementation plan, not the commission rate. However, they change depending on whether you can ship at all.

• Apple age rating update (deadline 31 January 2026): Developers must respond to updated age rating questions on every app or face submission interruptions. The updated ratings are only reflected on iOS 26 and later devices.
• Apple Xcode 26 requirement (from 28 April 2026): All apps uploaded to App Store Connect must be built with Xcode 26 or later using the iOS 26 / iPadOS 26 / tvOS 26 / visionOS 26 / watchOS 26 SDK.
• Apple Required Reason APIs (since 1 May 2024): Developers must declare approved reasons for the listed Required Reason APIs — including those used by third-party SDKs — in the privacy manifest.
• Apple’s EU Digital Services Act trader status (as of 17 February 2025): Apps without verified trader status have been removed from the EU App Store. Verification is mandatory for updates.
• Google Play Android 15 target (since 31 August 2025): New apps and updates must target Android 15 (API level 35) or higher; existing apps must target Android 14 to remain available to new users.
• Android 16 (API level 36) requirements: Apps must declare NEARBY_WIFI_DEVICES for local network access, migrate to granular health permissions (READ_HEART_RATE, READ_HEALTH_DATA_IN_BACKGROUND) with a mandatory privacy policy, adapt to forced adaptive layouts on 600dp+ screens, and expect predictive back animations by default.

The Android 16 large-screen rule matters for any app targeting tablets, Chromebooks, or foldables. Specifically, orientation, resizability, and aspect-ratio restrictions are ignored on 600dp+ screens. As a result, adaptive layouts become mandatory. A temporary opt-out exists. However, it will not apply once targeting API 37 is enabled.

Alternative distribution — what actually shipped in the EU

The DMA opened the door to alternative iOS distribution in the EU. However, two years in, the ecosystem is thinner than it was at launch. Setapp Mobile was one of the most visible early alt-store bets. It sunset on 16 February 2026, citing evolving and complex EU business terms. Three active EU-approved marketplaces remain as of mid-2026. First, AltStore PAL runs on self-hosted app sources with notable apps including UTM, OldOS, and iTorrent. Second, Epic Games Store on iOS has been live in the EU since August 2024, hosting Fortnite and other games. Third, Aptoide operates as an active EU marketplace and takes 10-20% commission on in-app purchases.

The Progressive Web App path remains available in the EU. Notably, Apple reversed its decision to remove Home Screen web apps. Consequently, the capability was restored in early March 2024 with iOS 17.4. However, EU Home Screen web apps still run on WebKit rather than the alternative browser engines permitted under the DMA. This is worth knowing for teams considering a PWA as their primary distribution channel.

For most commercial apps in 2026, the alternative distribution path is a secondary channel rather than a replacement. The App Store still owns the acquisition funnel.

The 2026 platform decision framework

Given the shifts above, five questions drive the actual platform decision in 2026. Answer them all before committing to a launch or expansion.

1. What is our annual proceeds trajectory? Under $1M USD, the standard Small Business Program (Apple) and first-tier program rate (Play) means both platforms cost 15% or less on a same-fee basis. Above $1M, the fee cliff on iOS non-subscription revenue is steep — model it into unit economics before scaling paid marketing.
2. Is our revenue subscription-based or transactional? Subscriptions past Year 1 hit 15% on Apple; Google Play subscriptions are 15% flat (or 10% + 5% billing in EEA/UK/US). Transactional in-app purchases are more expensive on both, and meaningfully so above $ 1 M.
3. Where are our users? If you have EU exposure, the DMA rules apply. If you are pursuing India or South Korea, the alternative-billing 4-percentage-point reduction on Play is real money. Southeast Asia mostly stays on the legacy commission structure.
4. Do we already operate a customer billing stack? External-payment link-outs make sense only for teams already operating web billing infrastructure at scale. For a mobile-first startup, a platform IAP is cheaper end-to-end, even at the standard rate, once fraud, VAT, and chargebacks are accounted for.
5. What is our tolerance for review-cycle risk? If your launch calendar has fixed dates, submit two weeks in advance for both stores. If your feature roadmap depends on frequent updates, the Google Play established-account fast lane matters more than the Apple update lane; plan your primary release cadence accordingly.

The right platform is rarely one or the other. For most Pegotec clients — industrial, NGO, and consumer — the answer in 2026 is both. However, primary metering should be placed carefully in the store where the fee arithmetic works best for the transaction pattern. The frameworks above are meant to make that placement deliberate.

Read next

• Flutter Development in 2026: What’s Changing and Why It Matters for Your Business — the framework side of a two-platform launch.
• Building Full-Stack Mobile Apps with Laravel, APIs, and Flutter in 2026 — the backend architecture that supports either store.
• App Store Optimization (ASO): Beyond SEO for Mobile Apps — once you have chosen your store, this is how you get discovered.