A Swift package that lowers SwiftUI-shaped views through a strict seven-phase pipeline. One App declaration drives three runtimes: SwiftTUICLI, SwiftTUIWASI, and embedded SwiftUI / Web hosts.
resolve → measure → place → semantics → draw → raster → commit .package(url: "https://github.com/GoodHatsLLC/SwiftTUI", branch: "main")
.product(name: "SwiftTUI", package: "SwiftTUI")
.product(name: "SwiftTUICLI", package: "SwiftTUI")Layout is recursive parent-child negotiation, not a global solver. State drives rendering, not the reverse. The phase order is enforced by DefaultRenderer, FrameArtifacts, and the regression suites.
Authored views collapse into the resolved tree.
Parents propose sizes, children choose.
Recursive layout assigns integer-cell rects.
Focus chain, accessibility, identity rolls up.
Per-cell glyphs and styles emit as commands.
Commands rasterize into a capability-aware surface.
Diff against last frame and stream ANSI/OSC.
The same @main struct App declaration flows into terminal-native binaries, WASI browsers via SharedArrayBuffer-backed stdin, and host-managed embeddings inside SwiftUI windows or DOM elements.
RunLoop over the alternate screen. ANSI / OSC 8 / Kitty / Sixel negotiated against the live capability profile. Unix signal handling, mouse reporting, and pty-backed secondary scenes ship by default.
import SwiftTUICLI
@main struct DemoApp: App {
var body: some Scene {
WindowGroup("Deploy Dashboard") {
BuildSummary()
}
}
}Build the same target to wasm32-wasi. The WASIRunner emits a scene manifest the host loads through GUI/WebHost — no terminal emulator, no xterm.js, no postMessage shim.
// build
swift build --swift-sdk swift-6.3.1-RELEASE_wasm \
--target WebExampleApp
// host
await createWebHostApp({
manifestUrl: "./scene-manifest.json",
sceneRuntimeFactory: createWasmSceneRuntimeFactory(...)
})Retain a HostedSceneSession in your SwiftUI view. Theme tokens swap at runtime; the authored TUI never sees the host.
SwiftUIHost(scene: deployScene)
.terminalTheme(.solarizedDark)
.frame(minWidth: 560, minHeight: 320)Drop a .terminal-shell div into a Bun, Astro, Remix, or Next page. The host owns chrome — the framework owns the cells.
<div class="terminal-shell"
data-scene="gallery"></div>
<script type="module" src="/host.js"></script>Layout primitives first. State and environment second. Runtime correctness third. Broader orchestration only after the foundation is firm. Terminal-only chrome that would bend the public authoring story does not belong in core.
At the lowest public runtime level, you can resolve and render any View into terminal text. Same code path your App takes inside RunLoop, exposed for tests, snapshots, and CI fixtures.
import SwiftTUI
struct BuildSummary: View {
var body: some View {
VStack(alignment: .leading, spacing: 0) {
Text("Deploy Queue").bold()
Divider()
ProgressView("Release", value: 18, total: 24)
LabeledContent("Window", value: "staging")
LabeledContent("Owner", value: "infra")
}
.padding(.init(horizontal: 1, vertical: 0))
}
}
let renderer = DefaultRenderer()
let frame = renderer.render(
BuildSummary(),
proposal: .init(width: 40, height: 8)
) Deploy Queue
────────────────────────────────────
Release
18 / 24
Window staging
Owner infra
_