SDKs
You pick the SDK for the platform your app runs on. All three wrap the same Rust core, trueseal-sync, and expose the same TrueSeal object with the same operations, events and errors, so a message sent from a Swift app arrives in a Kotlin app exactly as it would in another Swift app.
| SDK | Platforms | Install from | Package | Repo |
|---|---|---|---|---|
| Swift | iOS 16 and macOS 13 or later | Swift Package Manager, a binary target on GitHub Releases | trueseal-sync-swift | trueseal-sync-swift |
| Kotlin | Android, API level 24 or later | Maven Central | dev.trueseal:trueseal-sync | trueseal-sync-kotlin |
| TypeScript | Node.js 20 or later | npm | @trueseal/sync | trueseal-sync-ts |
The TypeScript SDK ships native binaries for macOS on arm64 and x64, Linux on x64 and arm64 with glibc, and Windows on x64. It doesn’t run in a browser, because devices talk to the relay over raw TCP, which browsers can’t open.
Kotlin is published for Android only. Kotlin on a plain JVM isn’t a published target in the preview.
Versions
The three SDKs and the core release together as one TrueSeal Release, starting at 0.6.0. They always share a version number, even when one of them hasn’t changed, so use the same version of each SDK across your apps. TrueSeal.info reports the SDK version and the two protocol versions it speaks.
Every SDK is 0.x during the preview, and any release may break the API, the wire format or stored data. Developer preview has the rules, and Upgrade Notes lists each breaking release.
Other languages
There is no Go SDK and no plain Rust SDK in the preview. A Rust app can depend on the core through its git tags, without a stability promise. Writing a client in another language means implementing the Protocol and passing the Sync-level test vectors.
Where the API is documented
The guides under Integrate explain each part of the API. The Agent Docs hold the complete reference, and each SDK’s README is a quickstart.