SDKs and platforms
Compare package names, application targets, and default storage.
Choose the package for your application's language and runtime. Native and WASIX packages are separate choices.
| SDK | Package | Application targets | Default storage |
|---|---|---|---|
| Rust | oliphaunt | Native desktop, Tauri | Temporary directory |
| Swift | Oliphaunt | iOS, macOS | Temporary directory |
| Kotlin | dev.oliphaunt:oliphaunt-android | Android | Temporary directory |
| React Native | @oliphaunt/react-native | iOS, Android | Temporary directory |
| TypeScript | @oliphaunt/ts | Node.js, Bun, Deno, Electron | Temporary directory |
| WASIX Rust | oliphaunt-wasix | Rust hosts | Memory filesystem |
| WASIX TypeScript | @oliphaunt/wasix-ts | Browser, Node.js, Bun, Deno, Electron | Memory filesystem |
| C ABI | liboliphaunt | Custom native bindings | Caller-prepared managed root |
Runtime differences
React Native uses the Swift and Kotlin native integrations. A Tauri app normally keeps its database in Rust and exposes application commands to the webview.
Choose WASIX TypeScript when the same application needs browser and desktop storage adapters. Choose native TypeScript for native desktop runtime modes.
Use Runtime support to compare persistent storage, local endpoints, and optional tools. Each SDK quickstart describes its platform setup.