Native iOS and Mac, same engine.
The Pylon sync engine, ported to Swift and kept at parity with TypeScript. Live queries, optimistic writes, offline reconciliation, and a Loro CRDT bridge — generate a typed Swift client straight from your schema.
$ pylon codegen client --target swift
# Generates a typed Swift client + models from your
# schema. Drop it into your Xcode project and call
# the same queries and mutations as on the web.- The full sync engine in Swift — not a thin REST wrapper
- Feature parity with the TypeScript engine; sync fixes ship to both
- Live queries and optimistic mutations with offline reconciliation
- Typed client generated from your schema: pylon codegen client --target swift
The engine, not an adapter
packages/swift ships the same sync engine the web client runs — reconciliation, the operation queue, optimistic rollback, snapshot pagination, the works — written in Swift. Your iOS and Mac apps get the same local-first behavior and the same guarantees as the browser, not a REST shim bolted on top.
Parity is a rule, not a hope
The TypeScript and Swift engines are held at feature parity by policy: every sync fix lands in both. That's what keeps a cross-platform product — a web app and a native Mac app on the same backend — from drifting into subtle data bugs on one side.
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 Swift views call the same queries and mutations by name.
Build it on Pylon.
One framework for your schema, sync, auth, functions, realtime, and SSR. Free to start.