storekit-macos

What problem does it solve?

macOS developers face unique challenges implementing in-app purchases and subscriptions with StoreKit 2, including platform-specific transaction handling for interrupted purchases, sandbox testing limitations compared to iOS, receipt validation differences between App Store and Developer ID distribution, and SwiftUI UI component integration quirks.

Core Features & Use Cases

• End-to-end StoreKit 2 implementation patterns: Complete code for product fetching, purchase flows, transaction listening, content delivery, and subscription status checking tailored to macOS 26+.
• macOS-specific platform guidance: Covers AppStore.sync() for restore flows, SKOverlay integration, Developer ID distribution constraints, and sandbox testing setup without the SKTestSession API available on iOS.
• Production-ready guardrails: Includes subscription state machines for all renewal states, revocation and expiration handling, server-side receipt validation patterns, and a comprehensive review checklist to avoid common implementation mistakes.
• Use Case: A macOS productivity app developer can use this skill to implement a tiered subscription model with monthly, yearly, and lifetime options, handle Ask-to-Buy flows for family accounts, and test purchases in Xcode sandbox before TestFlight release.

Quick Start

Use the storekit-macos skill to implement in-app purchases and subscription management for your macOS app, following the provided StoreKit 2 code patterns and macOS-specific best practices.