iced-rs

    iced-rs/iced

    A cross-platform GUI library for Rust, inspired by Elm

    32.0K stars
    1.7K forks
    218 GitHub watchers
    Updated Nov 8, 2026
    View on GitHub

    Build with Backblaze B2

    SDKs, agent skills, IDE extensions, and reference pipelines from Backblaze Labs. All open source.

    Explore Backblaze Labs

    Loading star history...

    Where it stands

    Rank, growth pace and release cadence relative to everything GStars tracks.

    No releases in the last 90 days; the most recent was 336 days ago, with 313 contributors on GitHub.

    Peaked at #28 in the weekly ranking the week of Jan 18, its best in the past year.

    Use Cases & Benefits

    • Provides a cross-platform GUI library for Rust with a simple, type-safe, reactive programming model inspired by Elm.
    • Offers a batteries-included API with modular, renderer-agnostic architecture supporting native and web platforms.
    • Use for building desktop applications with responsive layouts and built-in widgets in Rust.
    • Use for creating custom widgets and integrating async actions in Rust GUI projects.
    • Use for developing cross-platform user interfaces that leverage GPU or software rendering backends.

    Should you depend on it?

    License terms, project hygiene and risks, from GitHub metadata and GStars' snapshots.

    License

    MIT

    Permissive: commercial use, modification and redistribution are allowed with attribution.

    Community files

    • README: present
    • Contributing guide: present

    Watch-outs

    No watch-outs from GStars' checks.

    General guidance from repository metadata, not legal advice. How we score

    From the README

    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 and check out the issues.

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

    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:

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

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

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

    And that's everything! We just wrote a whole user interface. Let's run it:

    Read the book, the documentation, and the examples to learn more!

    Excerpt from the iced-rs/iced README on GitHub (MIT license). © its authors.Read the full README on GitHub

    Daily snapshots

    Stars gained per day, and how forks and open issues moved, from GStars' daily snapshots

    Forks

    1.7K+82

    Open issues

    524+46

    Compared with peers in Graphics

    Fastest-growing repositories GStars tracks in this cohort for the week of Nov 8, by 7-day star growth

    iced-rs/iced compared with Graphics repositories by stars, 7-day star growth, health score and last release
    RepositoryStars+7dHealthLast release
    heygen-com/hyperframes82.3K+4.0K75today
    boykopovar/AnyPS552.6K+1.9K5910 days ago
    mrdoob/three.js118.1K+5737511 days ago
    iced-rs/iced32.0K—42336 days ago
    playcanvas/engine17.2K—6423 days ago
    CadQuery/cadquery6.1K—47140 days ago
    Category median52.6K+1.9K64—

    Discover Repositories

    Search across tracked repositories by name or description