A cross-platform GUI library for Rust, inspired by Elm
Alternatives To Iced
Project NameStarsDownloadsRepos Using ThisPackages Using ThisMost Recent CommitTotal ReleasesLatest ReleaseOpen IssuesLicenseLanguage
Iced21,21317018 hours ago18July 28, 2023235mitRust
A cross-platform GUI library for Rust, inspired by Elm
Awesome Python Applications14,826
2 months ago38Jupyter Notebook
💿 Free software that works great, and also happens to be open-source Python.
11 hours ago59mitC
Embedded graphics library to create beautiful UIs for any MCU, MPU and display type. It's boosted by a professional yet affordable drag and drop UI editor, called SquareLine Studio.
Dearpygui11,489517 days ago220October 09, 2023254mitC++
Dear PyGui: A fast and powerful Graphical User Interface Toolkit for Python with minimal dependencies
a month ago145otherZig
zig game engine & graphics toolkit
a day ago152otherC
C++ Audio Plug-in Framework for desktop, mobile and web
Rui1,44712 months ago23May 31, 202314mitRust
Declarative Rust UI library
Fltk Rs1,3785514 hours ago360December 03, 20236mitRust
Rust bindings for the FLTK GUI library.
Gi1,2314119 hours ago110October 24, 2023171bsd-3-clauseGo
A free and open source framework for building powerful, fast, and beautiful 2D and 3D GUIs that run on macOS, Windows, Linux, iOS, and Android with a single pure Go codebase.
Core2d83625a month ago17June 10, 2023mitC#
A multi-platform data driven 2D diagram editor.
Alternatives To Iced
Select To Compare

Alternative Project Comparisons


Documentation License Downloads Test Status Discourse Discord Server

A cross-platform GUI library for Rust focused on simplicity and type-safety. Inspired by Elm.


Iced is currently experimental software. Take a look at the roadmap, check out the issues, and feel free to contribute!


Add iced as a dependency in your Cargo.toml:

iced = "0.10"

If your project is using a Rust edition older than 2021, then you will need to set resolver = "2" in the [package] section as well.

Iced moves fast and the master branch can contain breaking changes! If you want to learn about a specific release, check out the release list.


Inspired by The Elm Architecture, Iced expects you to split user interfaces into four different concepts:

  • State — the state of your application
  • Messages — user interactions or meaningful events that you care about
  • View logic — a way to display your state as widgets that may produce messages on user interaction
  • Update logic — a way to react to messages and update your state

We can build something to see how this works! Let's say we want a simple counter that can be incremented and decremented using two buttons.

We start by modelling the state of our application:

struct Counter {
    // The counter value
    value: i32,

Next, we need to define the possible user interactions of our counter: the button presses. These interactions are our messages:

#[derive(Debug, Clone, Copy)]
pub enum Message {

Now, let's show the actual counter by putting it all together in our view logic:

use iced::widget::{button, column, text, Column};

impl Counter {
    pub fn view(&self) -> Column<Message> {
        // We use a column: a simple vertical layout
            // The increment button. We tell it to produce an
            // `IncrementPressed` message when pressed

            // We show the value of the counter here

            // The decrement button. We tell it to produce a
            // `DecrementPressed` message when pressed

Finally, we need to be able to react to any produced messages and change our state accordingly in our update logic:

impl Counter {
    // ...

    pub fn update(&mut self, message: Message) {
        match message {
            Message::IncrementPressed => {
                self.value += 1;
            Message::DecrementPressed => {
                self.value -= 1;

And that's everything! We just wrote a whole user interface. Iced is now able to:

  1. Take the result of our view logic and layout its widgets.
  2. Process events from our system and produce messages for our update logic.
  3. Draw the resulting user interface.

Browse the documentation and the examples to learn more!

Implementation details

Iced was originally born as an attempt at bringing the simplicity of Elm and The Elm Architecture into Coffee, a 2D game engine I am working on.

The core of the library was implemented during May 2019 in this pull request. The first alpha version was eventually released as a renderer-agnostic GUI library. The library did not provide a renderer and implemented the current tour example on top of ggez, a game library.

Since then, the focus has shifted towards providing a batteries-included, end-user-oriented GUI library, while keeping the ecosystem modular:

The Iced Ecosystem

Contributing / Feedback

Contributions are greatly appreciated! If you want to contribute, please read our contributing guidelines for more details.

Feedback is also welcome! You can create a new topic in our Discourse forum or come chat to our Discord server.


The development of Iced is sponsored by the Cryptowatch team at

Popular Gui Projects
Popular Graphics Projects
Popular User Interface Categories
Related Searches

Get A Weekly Email With Trending Projects For These Categories
No Spam. Unsubscribe easily at any time.