Use this page with AI

Copy this into your coding assistant and add your request.

Read https://openiap.dev/docs/ecosystem 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 →

Ecosystem

OpenIAP defines the shared client purchase contract and ships native and framework SDKs. The Commerce Protocol standardizes the server-side commerce boundary independently of any provider or hosted service. If you are interested in joining the ecosystem, please contact hyo@hyo.dev.

Spec

openiapTwo protocols · client and commerceClient ProtocolApp-facing contract · type SSOT · v1.0.0

Core

openiap-googleKotlin · Play, Amazon, Horizon · 4.0.0Android and Fire OSHorizon OSopeniap-appleSwift · StoreKit 2 · 4.0.0iOS, macOS and tvOS

Libraries

types from @hyodotdev/openiap-client-protocol
expo-iapReact Native & Expo (Expo Modules)2 modules6.0.0Expo
ModulesVega OSAmazon Fire TV (Kepler) build targetOnsideAlternative iOS marketplace integration
react-native-iapBare React Native (Nitro Modules)1 module17.0.0React Native
ModulesVega OSAmazon Fire TV (Kepler) build target
flutter_inapp_purchaseFlutter11.0.0Flutter
kmp-iapKotlin Multiplatform4.0.0Kotlin Multiplatform
maui-iap.NET MAUI / C#3.0.0.NET MAUI
godot-iapGodot (GDScript)4.0.0Godot
and more … join the ecosystem

Independent server contract

Commerce ProtocolLifecycle · entitlements · events · signed delivery
Conforming providers
IAPKitVerification · entitlements · events · webhooks
@hyodotdev/openiap-client-protocol generates the type system for the core native packages and for every framework library, and the core packages are bundled into each library. The Commerce Protocol defines the portable server-side lifecycle, entitlement, event, and webhook contract independently of any implementation, and the providers listed under it implement that contract. Select any node to open its documentation or project.

Core

  • @hyodotdev/openiap-client-protocol: authored client GraphQL contract and type generator shared by all OpenIAP libraries.
  • openiap-google: Android library for Google Play Billing with native Kotlin implementation. Also provides openiap-google-horizon flavor to support Meta HorizonOS and openiap-google-amazon flavor to support Fire OS. Distributed to third party libraries for consistent bug fixes and features.
  • openiap-apple: iOS/macOS/tvOS library using StoreKit 2 with native Swift implementation. Distributed to third party libraries for consistent bug fixes and features.

Third Parties

The following libraries are included in the OpenIAP monorepo under libraries/ and are part of the ecosystem.

Server-side contract

The OpenIAP Commerce Protocol defines normalized transactions, subscription lifecycle, entitlement decisions, commerce events, and signed webhook delivery. A provider or self-hosted backend can conform without depending on a central OpenIAP service.