A Rust UI library that provides truly native, cross-platform GUI applications with multiple backend support.
Sauron-native is a Rust UI library that enables developers to create truly native, cross-platform graphical user interfaces for desktop, mobile, and terminal applications. It extends the Sauron web framework and supports multiple GUI backends including GTK, HTML, and TUI, allowing a single codebase to target different platforms while maintaining native performance and appearance.
Rust developers building desktop applications, terminal tools, or web apps who want a unified UI framework that works across multiple platforms with native performance.
Developers choose Sauron-native because it provides a single UI codebase that can target multiple platforms with truly native rendering, follows the predictable Elm Architecture pattern, and avoids the overhead of web-based cross-platform solutions while maintaining Rust's performance benefits.
Truly cross platform, truly native. multiple backend GUI for rust
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports GTK, HTML, and TUI backends from a single codebase, enabling deployment across desktop, web, and terminal environments with native rendering, as shown in the example scripts.
Follows the functional, state-driven Elm Architecture inherited from Sauron, providing predictable state management and UI updates that simplify debugging and maintenance.
Runs on Linux, Windows, browsers, and terminals from one codebase, reducing development effort while maintaining native performance on each platform.
Delivers truly native GUI experiences on supported platforms, avoiding the overhead of web-based cross-platform solutions and leveraging Rust's efficiency.
Many core UI components like container, scrollable, and slider are marked as TODO in the README, limiting out-of-the-box functionality and requiring custom work.
macOS support is not yet implemented, as indicated in the TODO platforms list, making it unsuitable for projects targeting Apple devices.
The project is labeled as WIP, leading to potential instability, breaking changes, and lack of production readiness, which may deter risk-averse teams.