Introduction
One shared core, three native SDKs for subscriptions, entitlements, and credits.
Rovenue ships three client SDKs — Swift (iOS/macOS/tvOS/watchOS),
Kotlin (Android/JVM), and React Native — all thin façades over one
shared Rust core (librovenue). The business logic (HTTP transport with
idempotency + retry, an on-device SQLite cache, foreground polling, receipt
validation, entitlements, credits, identity) lives in the core; each façade
exposes it idiomatically.
What the SDK does
- Drives the store purchase end-to-end: fetches offerings, triggers the native StoreKit 2 / Play Billing sheet, and validates receipts transparently.
- Checks a user's entitlements (cache-first, refreshed in the background).
- Tracks a credit balance and spends credits server-side, idempotently.
- Manages identity (anonymous → known user).
What the SDK does NOT do
- Bulk merges.
identify()auto-transfers a prior install's purchases to the current device, but programmatic bulk merging (e.g. platform migrations) is a server operation your backend triggers via the secret-key API.
Funnels
Funnels are the one authoring product for everything before the purchase — multi-screen onboarding, branching, and the paywall in a single document, built once and served on the web or natively inside your app.
Pick your platform in the Installation guide, then follow the Quick Start.