Are we GUI Yet?

The state of building user interfaces in Rust.

The roots aren't deep but the seeds are planted.

As a low level language, Rust is perfectly suitable for making user interfaces the old fashioned way, with native APIs. However, competing in today's world typically means supporting many platforms, and that makes using native APIs an unattractive option for many.

Rust's expressiveness and high level abstractions make it ideal for building intricate and complex user interfaces. Unfortunately, there is little consensus on what the best abstractions are.

There are a number of bindings available today to existing frameworks, but those looking for a mature, easy to use, and completely Rust-based solution will most likely find themselves out of luck.

Current approaches to building GUIs in Rust include interfacing with Electron and building GUIs with HTML (or a framework on top of it), while others have taken to using graphics APIs and various wrappers to emulate classical widgets. The cross platform parallel rendering engine Webrender, built for Servo and usable in Firefox Nightly, takes this latter approach and is multi-platform, but is more of a base for a GUI framework than one in itself.

Stay in the loop.

If you're working on or writing about GUIs in Rust, please contribute! Each news entry can either be a post contributed to the Repo or a link back to your blog, Reddit thread, etc. See README for details.

Here are the most recent posts on AreWeGuiYet:


Here are also some popular and reccomended community links submitted to the site:

Entity-Component-System architecture for UI in Rust by Raph Levien


Select a tag (or tags) below to only show relevant crates. All crates will be shown when no tags are selected.

  • Bindings
  • CSS
  • GTK
  • HTML
  • Immediate mode API
  • QML
  • Qt
  • WebRender
  • piet