Awards are deliberately provisional until campus receipts land. They identify which competitor deserves the next test slot for fast builds, fast loads, SwiftUI fidelity, animation depth, native portability, server-side Swift, or fallback grammar.
Provisional best all-around web lane
Ignite
Fast build and fast load path with Swift-authored static output.
- Why
- It is the cleanest current path for a public marketing site: direct web output, Swift source, and no npm manifest observed in the repository scan.
- Prove next
- Install in campus, render the wrkstrm page, record build time, static asset weight, Lighthouse-style load timing, and animation ceiling.
- Sharp edge
- Static output can look polished while hiding weak interaction depth; it has to prove rich motion, not only fast pages.
fast-build
fast-load
direct-web
swift-first
award
Best dynamic browser motion lab
ElementaryUI
Swift-authored browser runtime that can test state, DOM updates, and animated interaction.
- Why
- It has the strongest dynamic-browser ambition in the current catalog and is already marked build-now for the homepage pressure test.
- Prove next
- Run a real campus demo with frame timing, interaction latency, reduced-motion fallback, and browser bundle size.
- Sharp edge
- The BrowserRuntime npm surface is real pressure; JavaScript cannot quietly become the product boundary.
animation
dynamic-ui
wasm
npm-pressure
award
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
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
Best server-side Swift archaeology
SwiftWebUI
Server-hosted SwiftUI-like views over browser sessions.
- Why
- It keeps the server-side Swift campus honest about older runtime ideas that may still teach session, diffing, and render-loop constraints.
- Prove next
- Compile a minimal server fixture and test cold start, request latency, and state update semantics.
- Sharp edge
- Older architecture is useful evidence, not a default path; it must earn every modern claim.
server-side-swift
runtime
latency
architecture
award
Best minimum grammar reference
SwiftTUI
Terminal renderer that forces the smallest useful SwiftUI-like component grammar.
- Why
- It can pressure-test state, layout, and fallback semantics without hiding behind visual polish.
- Prove next
- Render the same homepage arc as a low-fidelity terminal fixture and compare state shape to the web candidates.
- Sharp edge
- Terminal elegance does not prove browser animation, but it can expose bloated abstractions quickly.
fallback
terminal
state-model
small-grammar
award