Solution

Native iOS and Mac, same backend.

The first-class Swift SDK runs the full Pylon sync engine — not a REST wrapper — so your native apps get the same live queries, optimistic writes, and offline behavior as the web. Generate a typed Swift client straight from your schema.

Start free →Read the docs
The problem

Cross-platform usually means the web app and the native app drift: different data layers, different caching, different bugs. A REST SDK on mobile loses the local-first behavior the web client has, and keeping two hand-written sync implementations honest is a losing battle.

How Pylon solves it
01

The engine, in Swift

packages/swift ships the same sync engine the web runs — reconciliation, the operation queue, optimistic rollback, snapshot pagination — written in Swift. Your iOS and Mac apps are local-first with the same guarantees as the browser, not a thin networking shim.

Swift SDKSync engine
02

Parity, enforced

The TypeScript and Swift engines are held at feature parity by policy: every sync fix lands in both. That's what keeps a web app and a native Mac app on one backend from diverging into platform-specific data bugs.

Swift SDK
03

Typed from your schema

Run pylon codegen client --target swift and get Swift models and a typed client generated from the same schema your backend uses. A Loro CRDT bridge handles rich collaborative state. Your SwiftUI views call the same queries and mutations by name.

Swift SDKDatabaseRealtime
Built with
Swift SDK
Native iOS and Mac, same engine.
Learn more →
Sync engine
Live queries, not polling.
Learn more →
Realtime
Rooms, presence, and authoritative shards.
Learn more →

Ship it on Pylon.

Scaffold an app in seconds, deploy free on Cloud, scale when you need to.

Start free →Explore the product