Skip to main content
sdk

SDK Compatibility Matrix

draft
Audience: developerUpdated 2026-08-02

Official status, versions, and outputs for every Binoban SDK.

1.0.0 is the first stable release across every SDK surface.

SDKStatusVersionPlatform / outputMinimum platformDistribution
Web SDKactivepending — see note belowBrowsernot yet publishedscript snippet, loaded from your host.sdkPath; no public npm package name yet
Native SDK — Androidactive1.1.0AndroidminSdk 21, compileSdk 35Maven Central: io.binoban.sdk:sdk-android:1.1.0
Native SDK — iOSactive1.1.0iOSdeployment target 12.0Swift Package Manager (binoban-sdk-swift, tag 1.1.0) or CocoaPods (pod 'binoban', '~> 1.0')
React Native bridgeactive1.0.0Android + iOS (bridge over the Native SDK)inherits the Native SDK floors abovenpm: @binoban/react-native
Node / Server-sidenot released—server-side—not public yet — use the Tracking API directly
Pending — do not build against these yet
  • Browser support floor. No minimum browser/engine version is currently declared for the Web SDK. Don't assume a specific floor; confirm with Binoban support if your audience includes older browsers.
  • Public Web SDK version. The Web SDK doesn't yet carry a public release version — the script snippet loads whatever your host.sdkPath serves. A versioned, publicly citable release for the Web SDK is pending.
Android — Maven Central availability

io.binoban.sdk:sdk-android is on Maven Central; 1.0.0, 1.0.1, and 1.1.0 all resolve. The Kotlin Multiplatform coordinate is io.binoban.sdk:sdk, which Gradle module metadata resolves to the right platform artifact.

What "active" means here​

active means the SDK is released and its documented method surface (see each SDK's own reference page) is safe to integrate against. It doesn't mean every optional feature is documented — check the relevant SDK page for gaps.

See also​