A lightweight Swift framework for In-App Purchases on iOS, macOS, tvOS, and watchOS.
SwiftyStoreKit is a lightweight Swift framework for implementing In-App Purchases on Apple platforms like iOS, macOS, tvOS, and watchOS. It simplifies the integration of StoreKit by providing a clean, block-based API to handle purchases, subscriptions, and receipt verification, reducing boilerplate code and complexity.
iOS, macOS, tvOS, and watchOS developers who need to integrate In-App Purchases, subscriptions, or receipt validation into their Swift applications.
Developers choose SwiftyStoreKit for its straightforward Swift API, comprehensive feature set (including subscription support and receipt verification), and cross-platform compatibility, making it easier to implement In-App Purchases compared to using raw StoreKit directly.
Lightweight In App Purchases Swift framework for iOS 8.0+, tvOS 9.0+ and macOS 10.10+ ⛺
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Provides a clean, block-based Swift API that abstracts away StoreKit's complexities, making IAP integration straightforward as highlighted in the README's 'Super easy-to-use block-based API' feature.
Handles consumable, non-consumable, auto-renewable, and non-renewing subscriptions, along with discounts and Apple-hosted content, covering most IAP needs documented in the features list.
Works across iOS, macOS, tvOS, watchOS, and Mac Catalyst, allowing consistent IAP implementation on all Apple platforms, as noted in the platform badges and requirements table.
Includes tools for remote receipt validation and purchase verification, simplifying a crucial part of IAP security with methods like verifyReceipt and verifySubscription.
The README admits that progress on supporting StoreKit 2 has stalled with 'little progress' and unanswered issues, leaving developers without access to Apple's modern IAP APIs.
The project is now community-led with the original author inactive, leading to potential delays in bug fixes and updates, as warned in the 'Contributions Wanted' and 'Maintainers Wanted' sections.
Deliberately does not persist IAP data locally, requiring developers to implement their own storage solutions, which adds complexity beyond the core framework as stated in the Notes.