[the__alchemist]

As someone who builds desktop apps:

Is there any reason I would use this over something cross-platform like EGUI? I am kind of over software being OS-specific; this is one of the biggest compatibility mistakes we've made. Along with the related process of making drawing pixels on a display a complicated process!

[vitorgrs]

WinUI made sense when windows actually had a proper design guideline, and touch was also the focus. So using WinUI was just easier as the controls were all following the guidelines, and if you wanted to offer a native experience, that was the best choice.

But it's been long gone that time where Windows had a minimum cohesive guideline.

[electroly]

Even if I wanted a Windows-specific UI, I still wouldn't choose WinUI 3. You can ignore it.

At my day job, I choose Windows Forms with Blazor mixed in. That's old reliable Win32 tech + modern web tech, without any modern Windows tech mixed in.

[reddalo]

Win32 is absolutely the best GUI system, you get the most clean, performant and easy-to-use results.

I wish Microsoft just sticked to Win32 instead of reinventing the wheel with worse solutions.

[tensor]

Support for accessibility.

[d3Xt3r]

egui might not be great for it, but Slint and Iced have decent accessibility support (via AccessKit).

[tensor]

That must be new. Last I looked access kit wasn’t integrated into iced.

[taffydavid]

Well, from egui's own page:

> If you want a GUI that looks native, egui is not for you. If you want something that doesn't break when you upgrade it, egui isn't for you (yet).

[imtringued]

I agree. If the OS vendors want application developers to target their native UI framework, they have to put in that work to make it seamless. As of right now, every OS vendor has an incentive to make their UI toolkits incompatible with each other to ensure vendor lock-in.

[mdasen]

I too don't want to write OS-specific stuff, but here's some counter arguments.

With egui, it's an immediate mode GUI rather than retained mode and that has trade-offs: https://github.com/emilk/egui#why-immediate-mode. It's going to use more CPU (and battery power), there can be jitter and things shifting after the initial rendering, and other stuff. I think egui is very different from most cross-platform and platform-specific libraries.

With .NET MAUI, you're getting native controls, but you're now using a layer that's trying to use native controls on the underlying systems that don't always align completely. A lot of things act mostly the same across systems, but some things don't totally.

With Flutter, your app is going to be larger in part because you're shipping a rendering engine, runtime, widgets, etc. Does it have the look and feel you want? Maybe. That's a bit subjective. Does it handle all the little things correctly? When I'm using an app, I want it to scroll like how I'm used to scrolling working on my system. If you have differently styled buttons, I don't care, but if the scrolling feels wrong, it's going to annoy me. And there's so many little things.

Frankly, one of the reasons why Electron often does well is that a lot of the little things "feel right" because the UI is essentially a Chromium-rendered web page which users are used to interacting with. But that has downsides too - shipping a web browser with your app and the memory usage.

Heck, Qt apps in Gnome or GTK+ apps in KDE can look/feel "off".

And it'll all depend on your ecosystem. Often cross-platform solutions are lacking in accessibility - sometimes completely missing, sometimes half-baked and it works in some parts and not in others or just is janky. Memory usage is often higher. Many little things that make an app feel right might not be there. Many have slower startup times since they're loading a bunch of stuff that native apps don't need to. And it really depends on what approach the cross-platform library is taking to determine what is going to cause pain.

So you kinda have to pick your poison and what's acceptable to you will vary depending on your goals and tastes. Maybe React Native is the way to go for you with lots of native controls available and the feel that provides and the performance and size is acceptable.

If you create a Flutter or Kotlin Compose Multiplatform or AvaloniaUI app and put it on the web, it's not going to feel right as something like HN does. Right-click, text selection, etc. are all going to be different or missing. If you're creating a solitaire game, maybe that doesn't matter - you get desktop and web in one go and it's not a big deal.

But you have to know what you're building to know if the trade-offs being made are good ones. This isn't meant to sound anti-cross-platform, but as someone who has suffered some pain in this area, I guess I just wanted to impart that it isn't all sunshine and rainbows. Some times it can still be worth it, but just go in with your eyes open.

[brokencode]

Not really. At least not directly.

But it is used to implement various parts of Windows, such as the File Explorer, so any improvements are helpful for general system performance.