Use this page with AI

Copy this into your coding assistant and add your request.

Read https://openiap.dev/docs/updates/announcements and https://openiap.dev/llms.txt. Follow the reading instructions, detailed reference, and linked guides relevant to my task before making changes.
Inspect my existing project and reuse its framework and conventions. Ask me for missing product decisions. Implement the requested behavior and run the applicable checks.
Show the working result, the commands and actual test results, and any remaining limitations. Keep your explanation brief.

My request: [describe what customers should be able to do]
See an example request →

📢 Announcements

Important news and updates about OpenIAP

Built with OpenIAP: explore the apps, share yours

🔗

October 9, 2026

Built with OpenIAP: reading, notes, games, and bookmark app tiles connected by a shared foundation

Seeing what people build is one of the rewards of maintaining open source. The updated OpenIAP showcase brings together community apps and open-source projects including Folo, Linkwarden, Notesnook, and Standard Notes.

Across OpenIAP packages, GitHub reports 3,300+ public GitHub dependents. These are package estimates; repositories using several packages may count more than once. Thank you to everyone building apps, contributing fixes, and sharing feedback.

Find your next inspiration

Search by app name, description, library, or GitHub repository, then filter by category and OpenIAP library. Apps are ordered by public Google Play download counts; apps without a count follow them.

Your app belongs here too

Built an app with OpenIAP? Open-source and closed-source apps are welcome. No public source code is required.

  1. Open the submission section and copy the prompt for your AI assistant.
  2. Share your app link or project and connect the Showcase MCP server if your assistant requires manual setup.
  3. Confirm the app details, contact email, and listing consent, then ask your assistant to submit. Keep the receipt ID to check its review status.

Explore the showcase and share your app →

Amazon Fire OS and Vega OS support

We are now backed by Amazon Developer!

🔗

August 19, 2026

Today marks a meaningful milestone for our team: We're thrilled to share that OpenIAP is now backed by Amazon Developer through open-source sponsorship and technical contributions.

This support helps us to enable In-App Purchasing (IAP) capabilities for apps on Fire TVs through the OpenIAP ecosystem.

For context, more than 300 million Fire TV devices have been purchased around the world. They are used for streaming shows, playing games, and watching live events. For example, if you have ever rented a streaming movie, you have gone through an IAP payment flow.

Fire TV sports interface displayed on a living room TV

Image credit: Amazon News

There are two operating systems that power the Fire TV experience across these millions of streaming media players: Fire OS and Vega OS. OpenIAP supports both through its SDK and runtime integrations: Fire OS uses the Android amazon flavor backed by the Amazon Appstore SDK, while Vega OS uses a separate Kepler runtime path for react-native-iap and compatible expo-iap apps.

Key Points

  • The Amazon Store Setup guide shows how each framework builds a Fire OS app for the Amazon Appstore.
  • The same Amazon Store Setup guide also covers Vega OS as a Kepler runtime target, not a Fire OS Android build. Expo detects a Vega project from its manifest.toml, and bare React Native for Vega uses Kepler dependencies plus manifest.toml.
  • Amazon Appstore IAP: OpenIAP maps Amazon types of purchases including consumables, entitlements, subscriptions, purchase updates, and fulfillment into the OpenIAP API standard.
  • Catalog identity: Product IDs stay aligned across Amazon Appstore, Amazon App Tester, app code, and Kit entitlement checks.

Note: OpenIAP will continue to operate independently with the same commitment to developer experience and cross-platform compatibility. Our core libraries remain MIT licensed and free to use.

OpenIAP 3: Xcode 27, Flutter SwiftPM, and a cleaner API

🔗

July 29, 2026

Xcode 27-ready. Flutter SwiftPM. The legacy clutter is gone.

OpenIAP 3 connecting purchase experiences across device platforms

OpenIAP 3 is our biggest contract cleanup yet. It connects Flutter's SwiftPM path to openiap-apple 3.0.0, adds guarded Xcode 27 and StoreKit 27 support, and removes the deprecated APIs, duplicate fields, legacy request shapes, and compatibility aliases that made cross-platform integrations harder to reason about.

What lands in OpenIAP 3

  • Guarded Xcode 27 and StoreKit 27 support brings subscription bundles and suites, verified offer-code redemption results, and new transaction metadata without dropping the documented older-OS fallbacks. Xcode 27-built UIKit hosts must also adopt UIScene; the release notes link the host migration checklist and the device examples exercise it.
  • Flutter 3.44+ resolves the OpenIAP Apple 3.0.0 native dependency through SwiftPM; older or SwiftPM-disabled projects retain the CocoaPods path.
  • The legacy surface is gone: purchase, verification, offer, billing-program, and platform-request models now use one canonical vocabulary across the supported SDKs.
  • IAPKit receipt verification, scoped keys, client payloads, catalog reads, and inbound App Store and Google Play webhooks keep their existing wire contracts.

Advance notice: deprecated APIs leave in the next majors

🔗

July 24, 2026

OpenIAP is defining one predictable removal window for its deprecated APIs and compatibility shims. Nothing is removed in a patch or minor release: the OpenIAP specification, openiap-apple, and openiap-google remove their deprecated OpenIAP-owned surfaces in 3.0.0. Framework libraries remove the same generated surfaces and their own shims only when each library reaches its independently versioned next major.

  • react-native-iap 16.0.0 and expo-iap 5.0.0
  • flutter_inapp_purchase 10.0.0
  • godot-iap 3.0.0 and kmp-iap 3.0.0
  • OpenIap.Maui 2.0.0

Flutter users should migrate custom Android payload fixtures and adapters to the canonical dataAndroid key now. The 9.6.1 retained originalJsonAndroid only as a temporary input fallback for the remainder of Flutter 9.x; the alias is not a public Purchase field and is removed in 10.0.0.

maui-iap

maui-iap is Now Available!

🔗

May 7, 2026 - maui-iap v1.0.0

We're excited to announce maui-iap, an official OpenIAP implementation for .NET MAUI! Starting from maui-iap v1.0.0, C# apps can use the same OpenIAP product, purchase, subscription, and listener model already used by the React Native, Expo, Flutter, Godot, and Kotlin Multiplatform libraries.

  • Native C# API - MAUI-friendly interface following the OpenIAP specification
  • Cross-platform - Supports iOS, Android, and macCatalyst from a single codebase
  • Type-safe - Generated C# records and enums for better IDE support and fewer runtime errors
OpenIAP meets MAUI
Showing 1-5 of 12 items