Developers

Build for sutraOS.

sutraOS is in design, and there is no SDK to download. What you can read today is the design itself: the guidelines every screen is drawn to, and the plan for the framework your app will be built on.

What you can read today.

Read now

The interface guidelines.

The rules every sutraOS screen is drawn to, before anything is built. The first topic written out in full here is Materials; principles, type, the accent and motion are set out on the Design page.

Read the guidelines

Read now

The roadmap.

Which stage brings which tools: the app framework arrives as a preview in Rust with the first release, and Swift follows in stage 2, before the API is called stable.

See the roadmap

Three languages, in turn.

  1. With the first release

    Rust

    The app framework ships first in Rust, as a preview.

  2. Stage 2, decided

    Swift

    A first-class language, with a declarative API in SwiftUI's style. It arrives before the API is called stable.

  3. Stage 2, proposed

    TypeScript

    Recommended for the same stage, and not yet decided.

The framework, as planned.

What AppKit and SwiftUI give every Mac app, sutraOS means to give every app, so the right thing is the default.

What your app codes against
sutraOS's own app framework, never the toolkit beneath it. Version one runs on libcosmic and Iced; the inside can change later without breaking your app.
What every app gets
Windows that reopen where they were; documents with autosave, versions and crash recovery; undo tied to the system timeline; menus and shortcuts made from the actions the app declares; permissions, accessibility and translation built in.
Apps that exist today
The Store installs apps from Flathub. GTK and Qt apps take the system's colours and accent through exported themes, and Electron and Tauri apps use the system web view.

What doesn't exist yet.

None of these is built. Each one arrives with its stage on the roadmap, and this page will say when.

An SDK
Project templates, live previews, a UI inspector, guideline and accessibility checkers, a profiler, and a signing and packaging command.
Developer documentation
Written in the same plain style as the system itself.
A stable API
The framework ships as a preview first. It is called stable only in stage 2.