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.

@hyodotdev/openiap 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: 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.