Exact – a new cross platform UI framework
A new experimental UI framework called Exact aims to deliver lightweight, cross‑platform native apps from a declarative DSL (“Contract”) plus TypeScript or Rust logic, with a design optimized for AI agents to generate and test UIs. Commenters are intrigued by the prospect of escaping Electron-style bloat and like parallels to systems such as QML or Slint, but raise concerns about its heavy reliance on LLMs, dense machine-written code, confusing “agent‑native” messaging, and the lack of Windows and Android support in this early alpha. Comparisons with Flutter and other mature toolkits highlight the tension between ambitious, AI-first developer tooling and the need for stable, human-friendly ecosystems.
Overall reaction
- Mix of excitement and skepticism.
- Enthusiasts see this as potentially “huge”: lighter, native-feeling apps, an alternative to Electron, and a new agent-friendly development model.
- Skeptics describe the project as unintelligible, overly abstract, and possibly “hallucinated” AI slop with lots of boilerplate.
Platform support & “cross‑platform” claims
- Many criticize the lack of Windows and Android support, arguing a cross‑platform UI that omits them misses most users.
- Others counter that it’s an early alpha; Android and Windows are on the roadmap, and “cross‑platform” need not mean “all platforms.”
- Some are interested in Linux support but note there are no screenshots yet.
Agent‑native design & LLM dependence
- Confusion and discomfort around “agent native”; some initially think it requires paid frontier models to be usable.
- Maintainers clarify agents are optional; humans can use dedicated editors and tooling.
- Design choices (formal constraints, error messages, clock control) are aimed at making UIs easier for agents to build and test.
- Several worry about prioritizing agents over human DX and broader dependence on LLMs for programming.
Contract DSL, architecture, and comparisons
- Contract (the UI DSL) reminds some of QML/Qt and Slint; others compare it conceptually to JSX or XAML.
- Concerns: complex expressions in the DSL, lack of a clear formal spec, and whether it will scale for arbitrary UI complexity.
- Some prefer JSX/TSX because it’s “just JS with markup”; others argue JSX’s expression-only control flow is limiting.
- Slint is cited as a similar but more mature Rust-based DSL framework; Flutter, Budo, iup-go, and native UIs are mentioned as alternatives.
Code quality, readability, and docs
- Linked JS files are extremely dense, almost minified; many infer they’re AI-generated and hard for humans to review.
- The README is criticized as “Claudish,” vague, and agent-focused, making it hard for developers to understand the architecture or timing model.
- People want more under‑the‑hood detail and worry about production readiness; current status is acknowledged as early alpha, with a rough 2–3 month horizon for production use.