Apple’s Mini Apps Partner Program is here, and it cuts App Store fees to 15% for qualifying mini apps hosted inside your native iOS app—if you meet a new set of technical and policy requirements. For marketplaces, super‑app plays, and AI chat hubs, the economics and compliance shape of your roadmap just changed. (developer.apple.com)

Illustration of iOS host app listing multiple mini apps

Why Apple made this move now

Let’s be blunt: mini apps aren’t niche. They dominate China’s app economy and are creeping into Western products, from chat platforms to shopping and games. Apple’s new program follows a reported deal with Tencent to take a 15% cut on WeChat mini apps and opens the same rate to everyone who qualifies. That resolves a long‑running dispute, aligns with how users already behave in “super apps,” and shores up Apple’s services revenue without a blanket 30% tax. (bloomberg.com)

There’s also regulatory gravity. Apple has been under pressure in the EU and U.S. to loosen App Store rules and clarify payments and linking. The Mini Apps Partner Program is a strategic, rules‑based path that exchanges technical compliance (age gating, commerce plumbing, refund telemetry) for a lower take rate. (apnews.com)

What exactly is a “mini app” on iOS?

Apple defines mini apps as self‑contained experiences built with web tech—HTML5 and JavaScript—executed inside a native host app. Mini apps can be games, utilities, commerce funnels, or services, but they are distinct from the host binary and must follow App Review Guideline 4.7 and its sub‑rules (manifests, moderation, privacy, etc.). (developer.apple.com)

Key nuance: to qualify for the 15% commission, the mini app must come from a third party that you don’t control—Apple’s definition of control covers direct, indirect, or shared ownership and management. Your own in‑house micro‑features don’t count for the discount. (developer.apple.com)

Apple Mini Apps Partner Program: what changed (and what didn’t)

Here’s the thing: Apple didn’t invent mini apps last week—Guideline 4.7 has allowed HTML5/JS software streamed or loaded post‑install for years. The new part is the formal program and the 15% rate, plus concrete technical requirements tied to safety and commerce. (developer.apple.com)

Commission: 15% on qualifying mini app IAP, with developers retaining 85%. (developer.apple.com)
Scope: iOS and iPadOS apps on the App Store that host third‑party mini apps. (developer.apple.com)
Must‑have tech: Advanced Commerce API, Declared Age Range API, App Store IAP, and the Send Consumption Information endpoint for refunds. (developer.apple.com)
Manifest: per 4.7.4, you submit a manifest enumerating hosted mini apps and metadata for review. (developer.apple.com)
SKU model: you don’t manage mini app IAP SKUs in App Store Connect; you create and manage them via the Advanced Commerce API. (developer.apple.com)

What didn’t change? You still own moderation, safety, and law compliance for third‑party code you host. Apple explicitly reiterates responsibilities around content filtering, reporting, and kid safety. (developer.apple.com)

Who benefits first?

If you operate a platform with third‑party experiences—think a chat app with bots and tools, a shopping app with merchant mini stores, or a gaming hub with HTML5 titles—the math gets friendlier. The 15% rate is especially meaningful if you previously avoided IAP due to margin pressure or relied on awkward web redirects that hurt conversion. Expect early motion in China (WeChat, Alipay ecosystems), but keep an eye on U.S. adoption across chat and AI‑centric apps that are standardizing on embedded tools. (theverge.com)

Data points, dates, and scope you can plan around

Apple publicly posted the Mini Apps Partner Program on November 13, 2025. The headline economics: 15% Apple commission on qualifying mini app IAP when the host app integrates the Declared Age Range API, Advanced Commerce API, and IAP, plus refund telemetry via the App Store Server API. Host apps must be on iOS/iPadOS, submit a manifest for review, and ensure every mini app meets Guideline 4.7. (developer.apple.com)

Media and market coverage connected the launch to Apple’s deal with Tencent over WeChat mini apps, while noting a broader developer opening. Analysts floated potential upside for Apple’s Services revenue, implying meaningful transaction volume flows through mini apps today. (bloomberg.com)

Let’s get practical: a 10‑step build plan to ship a compliant host app

I’ve shipped review‑sensitive iOS releases for marketplaces and fintech. If I were refactoring a host app for the Mini Apps Partner Program, I’d run this playbook:

Confirm eligibility: inventory your embedded experiences; tag which are truly third‑party and not under common control per Apple’s definition. If fewer than three partners qualify, recruit more before applying. (developer.apple.com)
Design SKUs and offers: model consumables, non‑consumables, and subscriptions per mini app. Decide what’s shared vs. isolated; Apple requires consumables not be shared across mini apps to qualify. (developer.apple.com)
Integrate the Advanced Commerce API: this is non‑negotiable for SKU creation, merchandising, and checkout. Plan 2–4 sprints if you’re re‑platforming from custom PSP flows. (developer.apple.com)
Implement Declared Age Range API: collect or infer the user’s age range with appropriate parental approvals. Wire the gating logic so mini apps and SKUs are filtered by age. (developer.apple.com)
Adopt IAP purchase flows: embed Apple’s IAP for mini app transactions. Budget time to reconcile your existing wallet, refunds, and receipts with Apple’s receipt and server notification model. (developer.apple.com)
Hook up Send Consumption Information: on refund requests, send consumption data back to Apple to inform decisions and reduce abuse. Add explicit privacy disclosures in your policy. (developer.apple.com)
Ship the manifest: enumerate every hosted mini app, metadata, and purchase mapping as required by Guideline 4.7.4. Treat this like a package registry—automate generation as part of CI. (developer.apple.com)
Content safety and moderation: enforce reporting, filtering, and block tools for each mini app, not just the host. Document the workflow; reviewers ask for proof. (developer.apple.com)
QA matrix: test device/region combos, age gating scenarios, failed purchases, interrupted flows, and receipt validation. Add synthetic SKUs for chaos tests.
Apply to the program: the Account Holder submits the request; expect to provide host app details, eligibility proof, and accept terms. Timebox comms with partners so legal and data flows don’t stall. (developer.apple.com)

Pricing, margins, and partner contracts

At 15%, you get meaningful headroom to share revenue with mini app partners while keeping contribution margins healthy. But don’t forget: the host platform still carries support costs, fraud risk, and moderation overhead. Build your rev‑share templates with explicit line items for refund liabilities (since you must provide consumption info) and for the operational SLA a partner must meet to stay listed. (developer.apple.com)

What about AI agents and chat “tool stores”?

Platforms adding AI‑powered tools or bot marketplaces can treat those as mini apps when implemented in HTML5/JS. The program creates a sanctioned monetization path for digital goods sold inside those tools with Apple’s IAP handling receipts and refunds—useful if you’re building a “super chat” model or an enterprise hub with vendor add‑ons. Media coverage already notes momentum for in‑app mini experiences beyond China, including Western apps that embed tools and games. (reuters.com)

Common pitfalls and review gotchas

Three patterns draw rejections fast. First, mixing your own micro‑features with partner mini apps and trying to push all purchases through the 15% track. Apple’s definition of qualifying purchases is strict. Second, skipping the Advanced Commerce API for SKU management because “we’ll add it later.” No API, no discount. Third, weak age gating or a generic “13+” checkbox—Apple expects functional gating wired to Declared Age Range and content filters. (developer.apple.com)

How does this compare to web links and alternative payments?

You’ll still see headlines about web links, alternate payments, and DMA‑driven terms in Europe. Consider this program a parallel track: if you want the 15% for mini apps, you run Apple’s commerce APIs. If your strategy leans on links or external PSPs, do the legal homework by region, but don’t expect the reduced commission to apply. (apnews.com)

UX patterns that convert (without getting you flagged)

Make the host app feel like a trusted marketplace, not an iframe graveyard. Use the Advanced Commerce API’s merchandising hooks to surface clear price and entitlement info per mini app. Keep purchase confirmation native (Apple sheet), then route back into the HTML5 experience seamlessly. Post‑purchase, show receipts and manage subscriptions in a single account screen—it reduces support tickets and pleases reviewers. (developer.apple.com)

Mini apps checklists you can lift into Jira

Technical readiness

Receipt flow mapped: purchase, cancellation, refund, and restore.
Advanced Commerce API integrated for SKU lifecycle and presentation. (developer.apple.com)
Declared Age Range API wired to content gating and catalog filtering. (developer.apple.com)
Manifest generator in CI with unit tests against schema. (developer.apple.com)
Server notifications and Send Consumption Information endpoint implemented. (developer.apple.com)

Policy and content

Guideline 4.7 obligations documented; moderation and reporting UI verified. (developer.apple.com)
Partner contracts include content standards, abuse response SLAs, and refund cooperation.
Privacy policy updated to reflect data sharing and refund telemetry.

Business and ops

Rev‑share templates with explicit 15% platform fee and refund clawback terms.
Finance reconciliation cutover plan (old PSP vs. Apple receipts).
Support runbooks: chargebacks, partial refunds, underage access escalations.

Case for speed: why shipping in Q4 matters

Holiday traffic plus fresh program attention means App Review will see a wave of submissions. Being early gives you placement leverage with partners and time to harden telemetry before peak usage. If you already host HTML5 experiences, you’re halfway there—the bottleneck will be Advanced Commerce API integration and cleaning up age gating. (developer.apple.com)

Developer mapping purchase and age gating flows on a whiteboard

Strategic implications for product leaders

Zooming out, Apple is acknowledging that distributed, lightweight app models are here to stay. For product teams, mini apps reduce the friction of partner integrations and accelerate experimentation: you can onboard a new vendor with a manifest and commerce hooks instead of shipping a new binary. For CFOs, the 15% rate can unlock categories—casual games, seasonal passes, premium utilities—that weren’t viable at 30% once you split with partners.

There’s a catch: the host app is the trust anchor. You’ll shoulder compliance and brand risk for third‑party content. Set up a certification program for partners (security review, content review, and a staged rollout process) and make removal swift when policies are violated. (developer.apple.com)

What to do next

Decide your platform thesis: will you be a host for third‑party mini apps in 2026? If yes, pick two beachhead categories and start partner recruiting now.
Kick off a two‑sprint spike on the Advanced Commerce API and Declared Age Range API. Treat it as a vertical slice with one real partner. (developer.apple.com)
Draft rev‑share templates with a refund policy that anticipates Send Consumption Information signals. (developer.apple.com)
Stand up a moderation council: policy, engineering, and support meet weekly during the pilot.
Apply to Apple’s Mini Apps Partner Program once your slice is stable and your manifest is clean. (developer.apple.com)

Need a seasoned build partner?

If you’re moving fast on a mini‑apps marketplace, our team has shipped regulated commerce, age‑gated flows, and complex App Review submissions. Explore how we approach platform builds on what we do, skim recent delivery examples in our portfolio, and reach out via contacts to get a scoped plan you can take to stakeholders this week. If you want to keep reading, our blog covers release‑driven tactics like framework upgrades and policy shifts that impact shipping.

Isometric illustration of modular app storefront for mini apps

Final word

Apple’s 15% pivot doesn’t magically bless every embedded feature with cheaper fees. It rewards platform builders who accept responsibility for safe commerce, age‑appropriate access, and clear refund signals. If you can meet the bar—and you’re willing to curate real partners—this is your moment to turn a single‑purpose app into a durable platform. Ship the vertical slice, tighten the loop with App Review, and start compounding third‑party value where it matters: inside your app, on your terms. (developer.apple.com)

Apple’s Mini Apps Partner Program: The 15% Pivot