logoalt Hacker News

chironjitlast Monday at 2:56 AM2 repliesview on HN

I've built apps with Iced, Dioxus and PopOS's version of Iced. Here is my opinion:

1) Iced requires you to style everything in their own styling methods. It's not as intuitive as CSS. I found that, coming from using CSS, I struggled to recreate the style to the same high bar I expected from websites using css.

2)LLMs are not as familiar with Iced's styling, and will struggle with helping you plus also dealing with the breaking changes between Iced versions. Same to a lesser extent with Dioxus

3) Dioxus is easier to build by hand and via LLMs since you just use CSS/tailwind CSS. That said, even Dioxus is rough on the edges, you occassionly get some weird bugs, that you just have to deal with

4)PopOS' Iced version is great if you're using it on PopOS specifically but will require you to install a separate style pack on other linux distros to get the styling of the windows to show correctly. It's more mature than the original Iced IMO, though it's opinionated styling(of it's starter boilerplate) may be less to your liking. While I haven't used it in some time, I would consider it an almost independent fork by now

5) Last but most important negative IMO of Iced and Dioxus is their release cadence. Iced 0.14 has now launched more than a year since 0.13. For some the stability is great, but for frameworks that are still maturing with lots of improvements pending, I think it's actually important to have faster release cadences so that you know issues you face are not left hanging for a fix for a year.

Now onto more practical stuff: 1) If you need simple, standalone apps, any one will work. I think this may be true for your app idea

If you need speed of change, multi platform, etc, you will likely end up with Tauri. In that case, you might as well use the front-end framework you like.

2) None of the frameworks give you a pathway to publishing except Tauri. Basically, only Tauri really puts that as part of its guide, and so when you are going to Publish, you will be using Tauri's guide anyway

3) If you need multi-processing, Dioxus is out of your option, or you will end up using Tauri with Dioxus as your front-end


Replies

mootodaylast Monday at 4:16 AM

Thank you, I appreciate the in-depth opinion! I think Tauri with SvelteKit is going to be my first prototype, likely followed by gpui because I'm impressed by Zed which is built with gpui.

Also, TIL about PopOS, thank you!

show 1 reply
airstrikelast Monday at 5:28 AM

you can use the iced master branch at any time to take advantage of the latest features.

besides, new releases have nothing to do with fixing your specific issues.

and the pop os fork has historically rebased to the latest upstream release so not sure why you think it's independent

show 1 reply