Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience our own tag's counts — open to see them
–Visits
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · visits, page views and clicks counted by our own tag, which counts more than our checked analytics; every figure rounded down · how we count

Iced review

Free#56 of 61 in Desktop App Development Frameworks

A free, open-source Rust UI framework with native and web targets, marked experimental.

3.7/10Editor score
Iced3.7 Visit Iced

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

Iced is an open-source GUI library for building graphical interfaces in Rust applications. Its API is inspired by Elm, structuring an app around state, messages, view logic, and update logic. It targets developers who want a reactive, type-safe approach to desktop UI, while also listing web support. The project is marked experimental by its maintainers, so it suits teams able to assess project status and roadmap before committing it to production more than those seeking a settled framework with commercial support.

The library’s core scope includes built-in widgets such as text inputs and scrollables, responsive layouts, and custom widget support. Asynchronous actions use futures. Debug tooling includes performance metrics and time-travel debugging, useful capabilities for inspecting application behavior as it changes. The native runtime is renderer-agnostic, with built-in wgpu and tiny-skia renderers. This gives Rust developers options within Iced’s rendering setup, but the product remains focused on UI development rather than a broader application platform.

Iced is free and open source under the MIT license, and its listed deployment model is self-hosted. Official project information lists Windows, macOS, Linux, and web; mobile targets are not included. Support channels are community resources and documentation, with no commercial support. That combination can fit solo developers and organizations of varying sizes that are comfortable relying on an open-source project and evaluating its experimental status. Teams that require mobile deployment, commercial support, or a more established production posture should consider alternatives.

Iced pros and cons

  • Where it wins
    • Type-safe reactive model with state, messages, views, and updates
    • Built-in widgets, responsive layouts, and custom widget support
    • Two renderers plus async actions and time-travel debugging
  • Where it doesn't
    • Maintainers describe the project as experimental
    • No verified mobile targets
    • Community and documentation support; no commercial support

Iced fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update