Apple Mini Apps Partner Program: 15% rate, requirements and fit
Apple now offers a defined route for native apps that host third-party mini apps: a 15% App Store commission on qualifying in-app purchases, in exchange for adopting a specific set of commerce, age and metadata technologies. The distinction matters because the lower rate is not a general discount. It applies only to a particular app pattern, with its own product, entitlement and refund handling.
What qualifies as a mini app
Apple's definition is narrower than everyday web content inside an app. A qualifying mini app is self-contained, uses HTML5/JavaScript, is downloaded after installation, runs inside a native host, and comes from a separate third party.
That third-party condition is the main filter. Wrapping your own feature in a webview, or reclassifying ordinary in-app screens, does not create a mini app for this purpose. The model Apple is formalising resembles the micro-experiences popular in ecosystems such as WeChat and Alipay, now given a structured route on iOS.
When the 15% rate applies
When an app qualifies and implements the required APIs, the host keeps 85% of eligible purchase revenue. Eligible product types are consumables, non-consumables, auto-renewing subscriptions and non-renewing subscriptions.
Two conditions must hold together: the purchase happens inside a qualifying mini app, and it uses the Advanced Commerce API. Classic App Store Connect products cannot be used for these flows. Consumables also carry a scoping guardrail: they belong to the mini app that sold them and are not shared across other experiences.
What joining requires
Participation is tied to a stack of newer App Store technologies rather than a simple enrolment toggle:
- Advanced Commerce API for configuring products and handling purchases
- Declared Age Range API so content is served appropriately
- StoreKit IAP as the payment system
- Refund consumption reporting via the App Store Server API
- Mini-app manifests carrying detailed metadata for each hosted mini app
In practical terms, the host takes on more integration and review work. In return, it gets clearer expectations than the previous grey area around apps-inside-apps.
Why platform-style apps should pay attention
For platform-style products, each mini app can operate as its own economic unit, with separate SKUs, entitlements and refund logic. That avoids forcing every third-party experience through one shared catalogue.
The economics also change: a 15% fee is more attractive to both hosts and the third-party builders inside them. On compliance, Guideline 4.7 has shaped this space for years; this program adds structure and reduces ambiguity about what Apple permits.
Who this is not for, and what to watch
If you do not host external developers, creators or partners, and do not plan to, this program probably does not change your roadmap. It is not a general shortcut to lower fees.
It is still worth watching strategically. Apple is creating formal space for apps inside apps, which could influence how mobile software is built over time. Early signals include cleaner rules for a messy grey zone, a clearer iOS path for markets with strong mini-app cultures, the Advanced Commerce API becoming central to future commerce features, and potential fit for JavaScript-based tools that let creators build lightweight experiences inside a host — provided those experiences meet Apple's third-party, HTML/JS, downloaded-after-install definition.
Decision checklist
Use this checklist before treating the program as an action item:
- Do you host, or want to host, third-party micro-apps or tools?
- Are those experiences built with HTML5/JS, or could they be?
- Does your strategy lean toward a platform or marketplace model?
- Are you prepared to integrate Advanced Commerce, Declared Age Range and structured mini-app metadata, plus refund consumption reporting?
If the answer is not a confident yes across the list, treat this as strategic context rather than immediate work. If you are building toward a platform, it is a clear signal: lower fees, more structure, and a defined path to hosting mini apps at scale.
| Check | Qualifying mini app | Ordinary app feature |
|---|---|---|
| Builder | Separate third party | Your own team |
| Technology | HTML5/JavaScript, downloaded after install | Native feature or webview wrapper |
| Commerce | Own SKUs, entitlements and refund logic via Advanced Commerce API | Standard host catalogue |
Based on Apple's definition in the captured material; confirm current program terms before implementation.
Frequently asked questions
What counts as a mini app under this program?
A mini app is a standalone HTML5/JavaScript experience, downloaded after the host is installed, running inside a native host, and built by a separate third party. A feature your own team built and placed in a webview does not meet that definition.
Which purchases can use the 15% rate?
Consumables, non-consumables, auto-renewing subscriptions and non-renewing subscriptions can be eligible when bought inside a qualifying mini app through the Advanced Commerce API. Classic App Store Connect products are not allowed for these flows, and consumables must be scoped to the mini app that sold them.
What must a host app implement to join?
Host apps need the Advanced Commerce API, Declared Age Range API, StoreKit IAP, refund consumption reporting via the App Store Server API, and structured mini-app manifests with detailed metadata for each hosted mini app.
Does this help a normal single-publisher app lower its fee?
No. The program is aimed at platform, marketplace and ecosystem apps that host external developers, creators or partners. A single-publisher app that does not host third-party experiences is unlikely to need it.