HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
iced-rs
iced
Rust2019–2026
iced-rs / iced

iced

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

54Distinct people
78Mentions
1Explicit recommenders
32KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

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

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

https://areweguiyet.com/ gives a broad overview, but is slightly outdated i believe. I recommend all raph linus' research on this topic, fairly recent blog:…

qwe098cube used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 6:28:55 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year78 dated mentions

Observed mentions: 2019-09-06 19:44:00 UTC to 2026-02-14 11:12:53 UTC.

0510152019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 6 mentions; 3 submissions, 3 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 14 mentions; 2 submissions, 12 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 10 mentions; 2 submissions, 8 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 11 mentions; 0 submissions, 11 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 12 mentions; 1 submissions, 11 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 17 mentions; 2 submissions, 15 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC633
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC14212
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC615
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC1028
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC11011
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC12111
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC17215
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC202

From the project README

An excerpt from the repository, fetched Nov 12, 2026.

Read the project’s introduction
Iced A cross-platform GUI library for Rust focused on simplicity and type-safety. Inspired by Elm. Features Simple, easy-to-use, batteries-included API Type-safe, reactive programming model Cross-platform support (Windows, macOS, Linux, and the Web) Responsive layout Built-in widgets (including text inputs, scrollables, and more!) Custom widget support (create your own!) Debug tooling with performance metrics and time traveling First-class support for async actions (use futures!) Modular ecosystem split into reusable parts: A renderer-agnostic native runtime enabling integration with existing systems Two built-in renderers leveraging wgpu and tiny-skia iced_wgpu supporting Vulkan, Metal and DX12 iced_tiny_skia offering a software alternative as a fallback A windowing shell Iced is currently experimental software. Take a look at the roadmap and check out the issues. Overview 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: #[derive(Default)] struct Counter { 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 { Increment, Decrement, } Now, let's show the actual counter by putting it all together in our view logic: use iced::widget::{button, column, text, Widget}; impl Counter { pub fn view(&self) -> impl Widget<Message> { // We use a column: a simple vertical layout column![ // The increment button. We tell it to produce an // `Increment` message when pressed button("+").on_press(Message::Increment), // We show the value of the counter here text(self.value).size(50), // The decrement button. We tell it to produce a // `Decrement` message when pressed button("-").on_press(Message::Decrement), ] } } 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::Increment => { self.value += 1; } Message::Decrement => { self.value -= 1; } } } } And that's everything! We just wrote a whole user interface. Let's run it: fn main() -> iced::Result { iced::run(Counter::update, Counter::view) } Iced will automatically: Take the result of our view logic and layout its widgets. Process events from our system and produce messages for our update logic. Draw the resulting user interface. Read the book, 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 library 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. Contributing / Feedback 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 Zulip forum or come chat to our Discord server. Sponsors The development of Iced is sponsored by the Cryptowatch team at Kraken.com
Read the full README on GitHub

What Hacker News says

14 sources
Project lead & contributor here. This software development effort has allowed us to test the hypothesis that we can build complex GUI software in Rust. We are building on the Iced[0] library, which has been a solid foundation so far. We're seeing high performance and low resource usage, as you would expect from a Rust program. And a single codebase gives us Windows, Mac, and Linux support with minimal fuss. [0] https://github.com/hecrj/iced/
In Built with Rust and Iced: Cryptowatch Desktop
Without plugging away at a specific language, I'm a fan of https://github.com/hecrj/iced. It's native cross-platform (Linux/Windows/Mac) and compiles to wasm for web support. Native as in no web rendering - it renders its own widgets via wgpu - but that's the compromise for easy cross-platform support. You use one interface for generic compatibility. This doesn't work for all cases, so you can also choose to add platform-specific code via conditional compilation to make sure that each platform's specifics are handled with intent, where you need to do so. It's exactly what you're looking for. Early stages - file support is a little rusty (pun intended) - but it's coming along fast.
In Tauri – toolchain for building secure native apps that have tiny binaries
Iced supports the desktop and the web. No mobile support but I don’t see why it couldn’t. https://github.com/hecrj/iced Technically, Qt has bindings and supports them too. So I don’t think your dream is too far off. Though the quality of that level of cross platform might be an issue
In Are We GUI Yet?
One of the things that use wgpu-rs is Iced[1], a cross-platform GUI Library inspired by the Elm Architecture. Although the project started around May 2019 and is still highly experimental, it looks like they got a lot of progress made and things look promising! The interest seems incredible: they have 5.4K stars on GitHub (amazing for such a young project) and there are lots of impressive examples[2]. As someone who just learned about the project: hope this takes off!!! A lightweight, simple to use GUI toolkit that can run on the browser and desktop is really something developers desperately want. [1] https://github.com/hecrj/iced [2] https://github.com/hecrj/iced/tree/master/examples
In Wgpu-rs on the web
Well, somehow I missed this one when looking for a GUI library in https://areweguiyet.com some time ago, and I was very surprised just now when it compiled and ran at first try: git clone https://github.com/hecrj/iced.git cd iced/ cargo run --package tour This ran the Tour example without any glitches, warnings, missing dependencies or any other annoyance. Don’t know yet whether this has what I need for my applications, but in any case it has left a very pleasant impression.
In Iced, a cross-platform GUI library for Rust

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.