Status
Platform support
Compare implemented and verified NatUI behavior on macOS and Windows.
NatUI is still in Alpha. Support claims distinguish implementation, compilation, and real-window verification.
| Capability | macOS | Windows |
|---|---|---|
| Native toolkit | SwiftUI | WinUI 3 |
| Base demo workflow | Real-window verified | Real-window verified |
| Kitchen-sink app-shell workflow | Real-window verified | Real-window verified |
| Node process mode | Verified | Verified |
| Embedded mode | JavaScriptCore verified | V8 verified |
| Native application package | .app | One self-contained EXE |
| Host build in CI | Yes | Yes |
| Headless package inspection in CI | Yes | Yes |
| GUI suites in CI | No | No |
Cross-platform component support
Both hosts implement all 37 public components, including their controlled-state, selection, presentation, and event paths. Individual component pages still describe platform-native conventions where the operating systems differ.
Implementation details
- Table uses a list-based fallback on macOS 14.0 through 14.3.
- Embedded execution uses system JavaScriptCore on macOS and V8 on Windows.
- Packaged applications validate their generated manifest, protocol, minimum host API, architecture, and SHA-256 entry digest before evaluation.
- The Windows single-file EXE extracts runtime dependencies to a per-user temporary cache at launch.
- GUI verification runs locally because the hosted CI jobs do not provide a normal desktop window session.
These are current implementation details, not promises of permanent behavior.