Flutter plugin to implement in-app subscriptions and purchases. Validate user receipts and manage cross-platform access to paid content on your app. Android & iOS.
Package selection guidance compiled from public package information, community data, and project usage.
Qonversion Flutter is a plugin that enables in-app subscriptions and purchases for Flutter apps on Android, iOS, and macOS. It simplifies receipt validation and manages cross-platform access to premium content. By integrating with Qonversion's backend, developers can securely verify user purchases and unlock features based on subscription status. The SDK handles platform-specific nuances, ensuring consistent behavior across devices. It supports both one-time purchases and recurring subscriptions, making it ideal for content-driven apps.
Use cases
Managing in-app subscriptions
Validating user receipts
Enabling paid content access
Supporting cross-platform subscriptions
Handling subscription renewals
Implementing tiered access levels
Key features
Cross-platform support (Android, iOS, macOS)
Automatic receipt validation
Unified access control for paid content
Real-time subscription state updates
Easy integration with Qonversion backend
Support for both subscriptions and one-time purchases
Suitable for
Apps with subscription models
Content-based mobile apps
Cross-platform apps needing unified access
Developers using Qonversion backend
Apps requiring secure purchase validation
Monetized apps with tiered features
Considerations
Requires Qonversion account setup
Depends on Qonversion backend services
Limited to Qonversion’s ecosystem
Needs proper configuration for each platform
May require additional server-side logic for custom rules
Not suitable for direct payment processing without backend
Original README
Original README snapshot from the linked source repository. Visit the repository for the latest content.
Qonversion
Qonversion - In-app subscription monetization: implement subscriptions and grow your app’s revenue with A/B experiments
In-app subscription management SDK
API and webhooks to make your subscription data available where you need it
Seamless Stripe integration to enable cross-platform access management
Subscribers CRM with user-level transactions
Instant access to real-time subscription analytics
Built-in A/B experiments for subscription business model
In-App Subscription Implementation & Management
Qonversion SDK provides three simple methods to manage subscriptions:
Get in-app product details
Make purchases
Check subscription status to manage premium access
Qonversion communicates with Apple or Google platforms both through SDK and server-side to process native in-app payments and keep subscription statuses up to date.
You can use Qonversion webhooks and API in addition to SDK to get user-level data where you need it.
Qonversion provides advanced subscription analytics out-of-the-box. You can monitor real-time metrics from new users and trial-to-paid conversions to revenue, MRR, ARR, cohort retention and more. Understand your customers and make better decisions with precise subscription analytics.
A/B Experiments
Qonversion's A/B Experiments feature provides everything required to quickly launch paywall and other monetization experiments, analyze results and roll out winning versions without releasing a new app build. Qonversion A/B Experiments include:
User segmentation by country, install date, app version, free/paying user
Traffic allocation
Advanced subscription analytics
Visualization of A/B experiments results
Statistical significance of the results
Roll out winning versions without app release with remote config
No headaches with Apple's StoreKit & Google Billing. Qonversion provides simple methods to handle Apple StoreKit & Google Billing purchase flow.
Receipt validation. Qonversion validates user receipts with Apple and Google to provide 100% accurate purchase information and subscription statuses. It also prevents unauthorized access to the premium features of your app.
Track and increase your revenue. Qonversion provides detailed real-time revenue analytics including cohort analysis, trial conversion rates, country segmentation, and much more.
Integrations with the leading mobile platforms. Qonversion allows sending data to platforms like AppsFlyer, Adjust, Branch, Tenjin, Facebook Ads, Amplitude, Mixpanel, and many others.
A/B test and identify winning in-app purchases, subscriptions or paywals.
Cross-device and cross-platform access management. If you provide user authorization in your app, you can easily set Qonversion to provide premium access to authorized users across devices and operating systems.
SDK caches the data. Qonversion SDK caches purchase data including in-app products and entitlements, so the user experience is not affected even with the slow or interrupting network connection.
Webhooks. You can easily send all of the data to your server with Qonversion webhooks.
Customer support. You can always reach out to our customer support and get the help required.
Convinced? Let's go!
Installation
Follow the installation guide. The iOS and macOS native dependency is resolved through Swift Package Manager when it is enabled in Flutter (opt-in since Flutter 3.24, on by default since 3.44) and through CocoaPods otherwise — see iOS and macOS native dependencies.
Check the full documentation to learn about implementation details and available features.
Help us improve the documentation
Whether you’re a core user or trying it out for the first time, you can make a valuable contribution to Qonversion by improving the documentation. Help us by:
sending us feedback about something you thought was confusing or simply missing
sending us a pull request via GitHub
suggesting better wording or ways of explaining certain topics in the Qonversion documentation. Use SUGGEST EDITS button in the top right corner.
Contributing
Contributions are what make the open source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.
Fork the Project
Create your Feature Branch (git checkout -b feature/SuperFeature)
Commit your Changes. Use small commits with separate logic. (git commit -m 'Add some super feature')
Push to the Branch (git push origin feature/SuperFeature)
