skills/monetization/external-purchases/SKILL.md
US web checkout via the StoreKit External Purchase Link entitlement — currently 0% Apple commission (litigation ongoing), how to ship it safely, and how to architect for a commission flip so a future ruling is a config change, not a rewrite. Use when adding external purchase links, weighing web checkout vs IAP, or planning US-storefront pricing strategy.
npx skillsauth add rshankras/claude-code-apple-skills external-purchasesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security scan pending...
This skill is queued for security scanning. Results will appear when the scan completes.
On the US storefront, apps may link out to a web checkout for digital goods using the StoreKit External Purchase Link entitlement — and as of mid-2026, court orders have Apple's commission on those purchases at 0%, with the fee case still moving through district court. This is the largest indie revenue unlock of the era, and it is reversible by a ruling — so the engineering rule is: ship it now, architect it so a commission can be flipped on later.
Verify current state before relying on this: the entitlement terms, the commission rate, and the litigation status have each changed more than once. Treat every number here as "true as of 2026-07, re-check."
com.apple.developer.storekit.external-purchase-link + matching
Info.plist declaration — a bare Link("Buy", …) without it is still a rejection (see
app-store/rejection-handler §3.1.1).ExternalPurchaseLink /
disclosure sheet where required). Don't dark-pattern the IAP option away if you keep both.Design so that a future "Apple takes N% of external purchases initiated in-app" ruling changes a config value, not your codebase:
source=app, timestamp, storefront) — web-organic checkouts stay unstamped. If a
commission returns, it applies to a knowable, logged subset.CommissionPolicy (remote-configurable): rate, applies_to,
effective_date. Report/accrue against it from day one — at 0% it's just a counter.openURL("https://…/buy") calls through features — un-auditable, un-flippable.| Situation | Lean | |---|---| | Subscriptions, US-heavy, ARPU high enough to absorb processor fees + your own support | Web checkout for new subs; keep IAP for the rest of world | | Impulse-priced consumables/unlocks | IAP — checkout friction eats more than 15–30% commission | | Existing subscriber base on IAP | Don't force-migrate; offer web at renewal decision points | | B2B/prosumer, invoicing needs | Web checkout regardless of commission math |
Status: entitlement present? · storefront scope correct (US-only gating)? ·
link-out service centralized? · CommissionPolicy flippable? · funnel analytics live?
Verdict + the one next step.
app-store/rejection-handler (the non-entitled rejection pattern), generators/subscription-lifecycle, monetization (pricing), growth/store-growth-audittools
Revenue beyond the single-app price tag — own-app bundles, Family Sharing as a conversion lever, cross-developer bundles & suites, and institutional licensing via Group Purchases / Apple School & Business Manager. Use when a developer has multiple apps, a subscription worth sharing, complementary indie partners, or school/clinic/business buyers.
testing
Run a structured accessibility audit on an iOS/macOS app — automated XCUITest audits, Accessibility Inspector, manual VoiceOver/Dynamic Type passes, and App Store Accessibility Nutrition Label evaluation. Use before release, when preparing Nutrition Label declarations, or for EU Accessibility Act compliance.
tools
Stage-by-stage audit of an app's App Store growth machinery against a 54-item P0–P9 playbook — every item scored from an App Store Connect MCP call, a codebase check, or an explicit question to the user, then routed to the skill or command that fixes it. Read-only on App Store Connect. Use for a growth audit or scorecard, a pre-launch growth plan, a quarterly re-audit, or "which growth levers am I missing."
development
Performance profiling and SwiftUI debugging skills — Instruments guidance, hangs, memory issues, slow launches, energy drain, unnecessary re-renders, and view identity problems. Use when an app is slow, janky, or resource-hungry.