Views, State, Observation, Gestures, and Animations: SwiftUI semantics, drawn in terminal cells.

TUI toolkits make you choose between a low-level draw loop and a widget set with its own novel state story.
SwiftTUI instead take the declarative model SwiftUI has proven — that interface is a function of state — and aims it at terminal cells. You declare views; the framework owns layout, focus, redraw, and the terminal itself.

Under the hood, every frame is lowered through a strict, inspectable pipeline (resolve → measure → place → semantics → draw → raster → commit), with no global solver, virtual DOM, or curses. Layout is deterministic and every frame is snapshot-testable.

Terminal first, not terminal only. When you need it, the same authored App (same view tree, same @State, same @FocusState, etc.) compiles for the browser as a static WASI bundle, for native macOS and iOS windows, and for Android.
Hosts display and run the app natively — not through an emulated TTY. No xterm.js, no libghostty, etc.

• State in, screen out. Views are a pure function of your app's state: change a value and the runtime recomputes layout and rewrites exactly the cells that changed.
• Useful components, focus based navigation. Buttons, text fields, pickers, sliders, scroll views, and charts, with a focus engine, tab traversal, keyboard chords. You compose behavior instead of hand-routing key events to widgets.
• Make the terminal dance Advanced functionality is ported from SwiftUI. Tap · drag · hover gestures, animations and transitions, images, and even mesh gradients, all behave like in SwiftUI.
• The terminal, negotiated for you. Truecolor, Kitty and Sixel images, OSC 8 hyperlinks, and mouse reporting are probed per session and degrade gracefully; one binary is correct in kitty, a bare SSH session, or CI. You write views, not escape codes.
• Developer ergonomics Your app compiles into a single fast executable with checked concurrency. Layout and state are type-checked at build time, and tests render frames as integer-cell rasters without a TTY.
• Batteries included, accessible by default. Default builds provide accessibility flags --reduced-motion, --cursor-follows-focus, and even --web for a browser view. Terminal conveniences like --no-color, and --ascii are similarly bundled.

Development happens on GitHub and Discord. Come ask questions, show what you are building, or talk through a contribution.