Which of these has effective accessibility support? I suspect if such a filter was applied there would be very few. Probably just the bindings to gtk, qt or appkit.
Yes please add accessibility support as a filter.
The state of building user interfaces in Rust
81–90 of 156 posts
Re: The state of building user interfaces in Rust
#82Possibly stupid question: if we are OK with using Arc everywhere in the UI (UIKit style), does that help?
Re: The state of building user interfaces in Rust
#83I’ve been really impressed with GPUI, particularly with Longbridge’s open source component library which provides a bunch of shadcdn-alike widgets that are really well implemented and come with a bunch of tailwind-like helper functions that make layout easy. The downside is that the dependency stack you need to do gui programming with rust is massive and the compile times are brutal. You can’t beat the application pe…
This is great. In recent years the Rust has been talked about so much in regards to the web
. It us getting better and more technologies are being developed tk further this. I am very impressed in what im seeing now. There are some amazing techniques.
Re: The state of building user interfaces in Rust
#84I also wanted to shout out https://ratatui.rs/.
Most of the time, I just want some UI. And TUI's are easier / more portable than GUI's.
Re: The state of building user interfaces in Rust
#85I tried to find a ELM style framework in Rust. And I couldn't find it in Rust and chose F# Fabulous instead.
Re: The state of building user interfaces in Rust
#86i've recently built a very complex healthcare application in dioxus and it's been a tremendous joy to work with. right now it's web-only, but the app does run fine as a desktop app when we need it. having SSR built in means that the UX is amazing - really complex pages load basically instantly, and it degrades just as easily for folks that haven't loaded the WASM. server functions were also fantastic to work with and…
I would love to see this @octernion. Im very interested in health care apps.
Re: The state of building user interfaces in Rust
#87I also have a horse in this race, would love to have it included! I'm building Hypen ( https://hypen.space ), a UI framework with a DSL that works in in Rust, TS, Go, Kotlin, Swift, and all over the place, as long as you can use WASM or binaries. Some cool things about it: - Renders natively on Desktop, Web (DOM and Canvas), Android and iOS. - Streaming-first (SSR), so you can stream native apps from the server - Cus…
I like your vision for Hypen and I sincerely hope that you can avoid the faith of every project that tried it before you! (all the toolkits that started as declarative, with clear logic/ui separation, eventually and inevitably add scripting and reinvent js/html).
That made me chuckle though:
Accessibility and i18n tooling:
This is in the plan - accessibility should be the easier one, with i18n tooling coming as more "platform calls" support comes online.
Re: The state of building user interfaces in Rust
#88I'm excited for Dioxus which is making their own HTML and CSS renderer and has its own independent browser called Blitz, so that's good for competition in the space.
Re: The state of building user interfaces in Rust
#89I would give a look to the creators of SpacetimeDB and their game that they've developed. Some of their work utilizing Rust was interesting.
Re: The state of building user interfaces in Rust
#90Which of these has effective accessibility support? I suspect if such a filter was applied there would be very few. Probably just the bindings to gtk, qt or appkit.
I think this article: https://www.boringcactus.com/2025/04/13/2025-survey-of-rust-... was the most exhaustive review of accessibility that I know of.
Nice! Thank you.