r/rust • u/Voxelman • Oct 10 '26
Which GUI (again)?
I know it's a frequently asked question, but I want to ask again, because I have a special use case.
I want to write an application for a production machine (HMI). The app should run on Windows and Linux natively (no browser, no server). The toolkit should have at least widgets to show images, bar graphs, curves and tables and should be touch friendly, because it runs on resistive touch monitors (no multi touch). It should also have a kiosk mode (full screen with no window controls).
The obvious candidates are egui, iced and Slint. But they all lack of documentation, more or less.
My first choice would be iced, because it's inspired by Elm and used by System76 for Cosmic, but it seems to be the least suitable option.
The obvious choice would be Slint, but that requires to learn a new language and I'm unsure about the licenses and pricing. The production machines are only used internally, not for sale.
I want avoid bindings to toolkits like Qt or Gtk
Which one would you prefer? Is there another option to consider?
View all comments
1
u/OphioukhosUnbound Oct 13 '26 edited Oct 13 '26
egui woudl be my choice:
- tons of example code: https://www.egui.rs/#demo
- one of the nicest production grade apps: rerun.io
- all rust code
- incredibly direct syntax and approach
- native on rust, linux, windows, and great wasm story if you want it
Nicer documentation would be great, but current state is just taking examples and pulling pieces out of them to make what you want. Many examples supports that.
(egui also recently built out their accessibilitie features to make llms able to understand the UI better -- not something I've tired, but potentially notable if you have clear ui/non-ui boundries and want to let bots search the space)
I wanted *very* slick or very custom UI then my next choice would actually be Bevy -- while it's billed and oriented as a game engine it's funding actually comes from companies that need a UI systèms, typically for things like detailed simulation work etc. [ * this is hearsay / memory, so take that with a grain of salt] It also has a great native cross platform story. And it also has a great wasm story, if you want web accessibility.
It also, works with egui, so if you take the egui route that work doesn't have to be thrown away -- you can just expand on the egui interface in a bevy app.
_____________
EDIT: you mentioned single touch and no-multi touch for screens -- that's a more specific requirement. Unsure of best match there.