SDKs
trueseal-sync is written in Rust. The SDKs below wrap that one Rust core through native bindings, so each language gets an idiomatic, statically-typed API without anyone having to re-implement the protocol three times and pray the implementations agree.
API reference, install instructions and integration examples live in each repo’s README. This page is just the entry point — pick a platform, follow the link.
Available
| SDK | Status | Repo |
|---|---|---|
| Swift | Production-ready | github.com/julianbonomini/trueseal-sync-swift |
| Kotlin | Available | github.com/julianbonomini/trueseal-sync-kotlin |
| TypeScript | Available | github.com/julianbonomini/trueseal-sync-ts |
Swift
iOS and macOS, distributed via Swift Package Manager. Wraps the Rust xcframework through UniFFI. This is the most mature SDK — it’s what trueseal-clip ships on both platforms.
Kotlin
Android and JVM, distributed via Gradle. Same UniFFI bindings against the same Rust core.
TypeScript
Node.js and Electron, with native bindings — not WASM. Browser is not a target. The protocol speaks raw TCP to the relay, and browsers can’t open raw TCP sockets.
Rust
If you’re already on Rust, skip the wrappers and use trueseal-sync directly. There’s no “Rust SDK” because there’s nothing left to wrap.
Other languages
- Go — planned, post-launch. The relay is already Go, so a Go sync SDK is the natural next thing.
- Anything else — implement trueseal-protocol. The wire spec is the only contract that matters; if your client speaks it, any conforming relay will talk back.