Data-oriented Rust UI design toolkit.
Raph Levien f0148cf335
Merge pull request #39 from futurepaul/new-widgets
3 days ago
ci Allow warnings 2 months ago
druid-shell Send mouse move messages when mouse is down (mac) 6 days ago
examples more cleanup 5 days ago
src more cleanup 5 days ago
.azure-pipelines.yml Move back to dotfile 2 months ago
.gitignore Initial minimal Windows app 2 years ago
AUTHORS Use druid in xi-win (#58) 6 months ago Update 7 months ago
Cargo.lock fleshed out menu interface 2 months ago
Cargo.toml Update to 2018 edition 2 months ago
LICENSE Opensource releasing love 2 years ago Update 6 months ago


Data-oriented Rust User Interface Design toolkit

Druid is a new Rust-native UI toolkit, still in early stages. Its main goal is performance, also aiming for small binary size and compile time, fast startup, and very easy build configuration (just cargo run). It is currently Windows-only, but with hope for porting.

Raph gave a talk at the July 2018 SF Rust Meetup (video, slides) about the design. Traditional object-oriented designs have proved to be cumbersome.

The layout protocol is inspired by Flutter. It is originally being developed primarily for use by xi-win, but has the potential to be useful for other applications. Due to its focus on performance and the relative paucity of toolkit-provided components, it is more likely to be useful for games and music software than general-purpose GUI applications. It is currently used as the basis for Synthesizer IO.

The druid-win-shell layer

The druid-win-shell layer is primarily an abstraction for displaying a window and receiving events. As such, it is an alternative to winit.

Ideally all Windows-specific logic (including all uses of unsafe) are isolated to the druid-win-shell subcrate, and druid proper is cross platform and with no unsafe code. That is not entirely the case now.


This crate is currently in early stages. More features will be built out as needed for use in the flagship apps, and this will inevitably lead to API instability. Features hoped-for soon include:

  • More of the basic widgets
  • Incremental presentation
  • Some simple theming support

The biggest single obstacle to porting is 2d graphics, as druid currently uses Direct2D (and DirectWrite for text). One way forward is to create a 2d graphics abstraction.


In addition to wrappers for mature UI toolkits (mostly C++), conrod and azul are interesting Rust-native efforts with promise to become usable.

With a focus on 2D games, ggez also looks promising.


We gladly accept contributions via GitHub pull requests. Please see for more details.

A very good place to ask questions and discuss development work is our Zulip chat instance, in the #druid channel.


The main author is Raph Levien.