Language Support

What each language does in a Jazz app, and what it doesn't support yet, compared with TypeScript.

Every language works from your app's TypeScript schema and permissions: npx jazz-tools generate writes each language's typed bindings from them. Your app's main backend runs in TypeScript (Vercel or your own server).

Rust, Swift, Kotlin and Go are experimental: they are clients of that TypeScript backend. All four can be apps, signed in as one of your users; Rust and Go also run as backend clients, services that act with a machine credential. None of them runs a main backend yet. Each tab lists what that language supports and what it doesn't yet, compared with TypeScript.

Experimental. Rust is a client of your TypeScript main backend's /jazz, in two roles: an app signed in as one of your users (Config::user, with device accounts or bearer sign-in, and JazzSession), or a backend client, a service with a machine credential, trusted or scoped, with for_user on a trusted client. It has queries with includes, select, hops, gathers and unions, history reads and subscriptions, partial reads (Query::part), branches and drafts, streaming uploads, mergeable text, permission advice, guests (device accounts), positions in subscription deltas, and close(timeout). See Rust and Backend Client.

It doesn't support yet:

  • running your app's main backend (serving its /jazz and publishing its permissions): run it in TypeScript with createJazz;
  • a built-in secure store (keychain) for device keys: the app keeps the key itself;
  • cookie sessions renewed in place: a Rust client signs in with a bearer and reconnects with a fresh one;
  • the browser-only parts of TypeScript's session: focus and visibility re-checks, cross-tab sign-out, clearOnSignOut and the thin-client upgrade.