Reference specimen

SwiftCrossUI

Cross-platform declarative UI as an API compatibility reference.

Many worlds. One workstream.

renderer Native shell maturity Investigate maintainer External upstream campus Campus maintainer candidate mode Native Swift reference npm No npm manifest observed setup Syntax specimen only import SwiftCrossUI

Shipping question

Can a cross-platform SwiftUI-like app validate the same component model before a web backend exists?

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 Package.swift and no npm manifest or lockfile paths.

Package: https://github.com/moreSwift/swift-cross-ui

current provisional award

Where this competitor is strongest.

Best native cross-platform reference

SwiftCrossUI

Native declarative UI reference for testing component grammar before web output exists.

Why: It gives wrkstrm a Swift-first way to test whether the component model is portable beyond browser concerns.
Prove next: Build a native fixture that mirrors the public page state model and records compile time, launch time, and platform gaps.
Sharp edge: Reference-only paths can improve architecture without ever shipping the web surface investors see.

native-reference cross-platform swift-first build-time 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 SwiftCrossUI
struct WrkstrmHome: View {
  var body: some View {
    VStack {
      Text("wrkstrm")
      Text("Many worlds. One workstream.")
    }
  }
}