ElementaryUI is a bet that Swift developers would rather stay in Swift than learn React. The framework maps SwiftUI's declarative API — @State, @Environment, body computed properties — onto HTML and CSS via WebAssembly compilation, producing kB-sized bundles instead of the multi-MB payloads typical of other Swift-to-Wasm toolchains. It ships with a Vite-powered dev server for hot reload, which means the development loop feels like modern frontend work rather than a cross-compilation science project. The pitch is straightforward: if you already think in SwiftUI's mental model — structs conforming to View, reactive property wrappers, declarative composition — then building a web UI should feel like building an iOS widget. The code sample on the landing page is a counter component that reads like SwiftUI with HTML element names swapped in for native views. Button, p, onClick, @State — all present and accounted for. What makes ElementaryUI interesting is the Embedded Swift angle. Apple's Embedded Swift subset strips out the runtime metadata and reflection machinery that normally bloats Swift binaries, which is what makes kB-sized Wasm bundles possible. This is a genuine technical lever, not marketing. Most Swift-to-Wasm projects inherit the full runtime and produce bundles that make React look lean. ElementaryUI sidesteps that entirely. The animation system leans on CSS transitions rather than reimplementing animation from scratch in Wasm, which is the right call — let the browser do what it's good at. FLIP transitions (First, Last, Invert, Play) for layout animations are included, which is a surprisingly mature feature for an early-stage framework. Most new UI frameworks ship animations as an afterthought. The honest limitation is ecosystem. SwiftUI has a massive surface area — navigation stacks, sheets, gestures, accessibility APIs, layout priorities — and ElementaryUI necessarily implements a fraction. The question isn't whether the API is pleasant (it clearly is) but whether it can handle a real application with routing, forms, authentication flows, and the thousand paper cuts of production web development. This is an open-source project sustained by sponsorships, which means its trajectory depends on community adoption and contributor momentum. The Swift-on-the-web niche is small but real — there are iOS teams that would love to share logic or even UI code between native and web targets without maintaining a parallel TypeScript codebase. Whether that niche is large enough to sustain a framework is the open question. ElementaryUI doesn't need to beat React. It needs to be good enough that a Swift-native team can ship a web dashboard or internal tool without context-switching to an entirely different language and paradigm. On that narrower ambition, the technical foundations look sound.
