Docs · Chapter 2 of 10

SDKs

Tierux client SDK overview — native Android and iOS, plus REST-first framework guides for React Native, Flutter, TypeScript/Node, and Expo.

1

Native SDKs

Tierux provides native SDKs for the two primary mobile platforms. Both handle purchase flow and server-side verification — your API key never ships in the client binary. The public app_xxx ID used below comes from create_project or the Tierux dashboard.

2

Android SDK (Kotlin)

Self-hosted Maven repository at https://maven-tierux.web.app. Add the repo and dependency, initialize with your app ID, and call Tierux.showPaywall(). Full paywall rendering, Google Play Billing, and server-side verification in one call.

// settings.gradle.kts
maven { url = uri("https://maven-tierux.web.app") }

// app/build.gradle.kts
implementation("com.tierux:android-sdk:0.2.0")

// Usage
Tierux.init(context, appId = "app_xxx", baseUrl = "https://tierux.com/")
Tierux.showPaywall(activity, "pro") { result ->
  when (result) {
    is PaywallResult.Purchased -> if (result.active) unlockPro()
    PaywallResult.Cancelled -> Unit
    is PaywallResult.Error -> showError(result.error)
    is PaywallResult.WinbackAccepted -> unlockPro()
  }
}

Full Android SDK guide →

3

iOS SDK (Swift)

Swift SDK source served via API — browse or download. Integrate locally with SPM (.package(path: "Tierux")). Full StoreKit 2 purchase flow and server-side JWS verification.

// Package.swift
.package(path: "Tierux")

// Usage
Tierux.shared.configure(appId: "app_xxx")
Tierux.shared.showPaywall(from: viewController, paywallId: "pro") { result in
  switch result {
  case let .purchased(_, _, active, _, _): if active { unlockPro() }
  case .cancelled: break
  case let .error(error): showError(error)
  case .winbackAccepted: unlockPro()
  }
}

Full iOS SDK guide →

4

REST-first frameworks

For cross-platform and non-native frameworks, Tierux uses a REST-first approach. Your app captures purchases via any IAP library, sends the token to your backend, and your backend calls Tierux's REST API for verification.

Native wrapper SDKs for React Native (@tierux/react-native) and Flutter (tierux_flutter) also exist in-repo today — not yet published to npm or pub.dev, but installable now via source download for React Native and source download for Flutter. See the platform support matrix for current limitations.

5

Framework-specific guides

React Native

Verify purchases server-side with react-native-iap or any IAP library.

Flutter

Use in_app_purchase or flutter_inapp_purchase, verify from your backend.

TypeScript/Node

Check entitlements and verify purchases from Node.js — plain HTTP.

Expo

Server-side verification with expo-in-app-purchases, no native module.

6

SDK security model

All Tierux SDKs and framework integrations share the same security model:

  • No client-side API keys — your server-side key never ships in the app binary
  • Server-side verification — purchase tokens are verified by Tierux's servers, not the client
  • Remote config — paywall layouts and copy are fetched from Tierux at runtime, changeable without an app release
  • Normalized state — all SDKs return the same entitlement response shape regardless of platform
Related docs

Docs: MCP Setup

Use your AI agent for Google Play infrastructure and Tierux-side product configuration. App Store Connect product and notification setup remains manual before SDK integration.

Docs: StoreKit

Deep dive on Apple StoreKit 2 JWS verification used by the iOS SDK.

Docs: Platform Support

The full per-feature capability matrix — what's production-ready vs in progress, per store.

Quickstart

Checklist for Tierux configuration, required store-console work, REST integration, and purchase verification.

Pick your SDK and ship

Free tier — unlimited apps, 1 paywall. No credit card, no revenue share.

Start free