A Swift framework for adding patronage features to iOS apps using CloudKit and In-App Purchases.
PatronKit is a Swift framework that helps iOS developers add patronage features to their apps, enabling users to donate via In-App Purchases and track patronage data through CloudKit. It solves the problem of monetizing free apps by encouraging voluntary user support through a structured donation system.
iOS developers looking to implement a patronage or donation model in their free apps, particularly those using Swift and CloudKit for backend services.
Developers choose PatronKit for its pre-built UI components and seamless integration with CloudKit and In-App Purchases, reducing the complexity of adding patronage systems and fostering user engagement through transparency and community metrics.
A framework to add patronage to your apps.
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 ready-to-use PatronageViewController that displays purchase options, reducing development time for implementing patronage systems without custom UI work.
Leverages CloudKit for seamless backend storage of patronage data, handling record zones and default containers automatically, which simplifies data persistence without server setup.
Integrates with Apple's In-App Purchases for transactions, specifically optimized for consumable products with identifiers ending in month numbers, streamlining donation processing.
Displays donation tallies and expiration dates to encourage user participation, fostering transparency and community support through built-in metrics.
Written in Swift 2 for Xcode 7.2, which is obsolete and may cause compatibility issues with modern Swift projects, requiring manual updates or workarounds.
Lacks support for CocoaPods or other package managers, forcing manual integration via dynamic framework, which can be error-prone and time-consuming for teams.
Requires In-App Purchase identifiers to end with a number representing months (e.g., 'com.patronkit.3'), limiting flexibility in product naming and structure.
The README lists To-Do items like improving patron count display and review count UI, indicating missing features that developers must implement themselves.