2021-10-12
3431
#rust
Mario Zupan
71564
Oct 12, 2021 ⋅ 12 min read

Iced.rs tutorial: How to build a simple Rust frontend web app

Mario Zupan I'm a self-employed Software Engineer and Trainer living in Vienna, Austria. I've worked at several companies and in multiple fields building, maintaining and operating distributed systems at scale using Java, Kotlin, Node, Go and Rust. I also taught advanced software engineering courses for several years at the University of Applied Sciences FH Joanneum in Graz and worked as a technical trainer, empowering other software engineers to reach their full potential. Currently, I work as a freelance software engineer and trainer again, looking to help companies build high-quality software solutions. Check out my personal blog: http://www.zupzup.org.

Recent posts:

Wasm 3 Before GTA 6 LogRocket Article

We got Wasm 3.0 before GTA 6: Meet the web’s new engine

Discover how WebAssembly 3.0’s garbage collector, exception handling, and Memory64 transform Wasm into a true mainstream web platform.

Ikeh Akinyemi
Oct 3, 2025 ⋅ 2 min read

How to use AI to build accurate ShadCN components

AI agents often break shadcn/ui components with outdated docs or made-up props. The MCP server fixes this by giving live access to registries. In this tutorial, we’ll set it up and build a Kanban board to show it in action.

Chizaram Ken
Oct 3, 2025 ⋅ 5 min read
Rust Project for Web Services LogRocket Article

The best way to structure Rust web services

Learn how to structure Rust web services with clean architecture, Cargo workspaces, and modular crates for scalable, maintainable backends.

Jude Miracle
Oct 2, 2025 ⋅ 2 min read
andrew evans headshot

A spec-first workflow for building with agentic AI

Andrew Evans gives his take on agentic AI and walks through a step-by-step method to build a spec-first workflow using Claude Code.

Andrew Evans
Oct 1, 2025 ⋅ 18 min read
View all posts

4 Replies to "Iced.rs tutorial: How to build a simple Rust frontend web app"

  1. This is a simple tutorial that expects the reader to know what “trunk” is and how to install / use it. Also there are just too many details that are being brushed over and the order creation is sometimes reversed. I get confused as to what file the tutorial is currently in. And for me, separation into several files for the sake of clarity would be obvious. This tutorial is a nice read. but not very good as a practical example. It was not for me.

  2. I agree with the prior comment. At least add on top of the code which file you are currently editing. It is mentioned once or twice but then brushed over as we change between files later. The more clarity the better.

    I could not completely follow this example to reproduce the build so it was not useful for me in determining if this is something I want to commit more time into learning.

    1. Hey Phil! We had Mario take a look at the article, and we posted an update up to that says the following: “Update 08/21/2024: Originally, Iced was focusing more on the web when this article was written, but since then, they’ve intensified their focus towards native GUI. Updating your dependencies based on this article will not work. We will update this article if anything changes on that front.” Thanks for bringing this to our attention.

Leave a Reply