Reference specimen

SwiftOpenUI

SwiftUI API compatibility research for non-Apple renderers.

Many worlds. One workstream.
renderer Native compatibility maturity Investigate maintainer External upstream campus Campus maintainer candidate mode Dynamic frontend with Swift npm npm present in web build setup Repository and setup to confirm import SwiftOpenUI

Shipping question

Can SwiftUI-compatible declarations become a portable compatibility target for web and native backends?

This specimen is generated by the wrkstrm homepage model. It does not prove the upstream framework is installed in the campus until a setup receipt lands here.

npm evidence: 2026-05-18 recursive GitHub tarball scan found web/package.json; package scripts use Vite, Node, and Puppeteer around the WASM web demo.

Package: https://github.com/codelynx/SwiftOpenUI

current provisional award

Where this competitor is strongest.

Best SwiftUI compatibility research

SwiftOpenUI

Compatibility harness for SwiftUI-shaped declarations across renderer backends.

Why
It is the sharpest catalog entry for asking what a portable SwiftUI API actually has to preserve.
Prove next
Separate demo-harness convenience from production runtime, then measure screenshot receipts against native SwiftUI expectations.
Sharp edge
Its web package uses Vite, Node, and Puppeteer; useful harnesses are not automatically production paths.
swiftui-fidelity compatibility screenshots npm-pressure award

Homepage arc

candidate

Generate possible worlds

Agents and digikomas produce apps, documents, diagrams, releases, and decisions.

parallel

Compare timelines

Shipped, stalled, counterfactual, and next-best branches stay visible together.

proved

Select the executable path

Schemas, Swift packages, DocC, receipts, commits, and releases back the branch.

Adapter sketch

import SwiftOpenUI
struct WrkstrmHome: View {
  var body: some View {
    NavigationStack {
      Text("Many worlds. One workstream.")
    }
  }
}