ModernWpf VS Windows UI Library

I was just googling around and found this page. https://wpfui.lepo.co/ maybe it something you can use. Or this github repo https://github.com/Kinnara/ModernWpf

At least there is WPFUI and ModernWPF. :)

Only really works if you or your users are a fan of Material Design, and honestly MD seems to have declined in usage overall, and there are no big apps for Windows using MD. Seems like you'd be better off with either a totally radical design/theme, and have the design resources to do that, or use something that looks like a native Windows app, whether thats the Win32 look, WPF defaults, or something WinUI inspired like https://github.com/Kinnara/ModernWpf

ModernWpf and WpfUI are both great options for making modern looking WPF apps. Combine that with CommunityToolkit.Mvvm and you've got a solid platform for Windows-only desktop apps.

This one looks pretty solid. There are loads of them. The demos I’ve seen all showcase live feedback.

https://superguigui.github.io/simple-color-picker/

Compare to the best I can find for WPF: https://github.com/dsafa/wpf-color-picker - no live feedback, dialog only, no documented support for modern .NET. There are some commercial controls available from syncfusion and the like if you want to pay for such things.

Compare to color dialog in WinForms: https://github.com/Kinnara/ModernWpf/issues/72

WinUI has a decent color picker, but there are other trade offs going with WinUI that make it inferior to the web environment (e.g. broken rendering of SVG/paths).

ModernWpf (whose status is unclear) has it: https://github.com/Kinnara/ModernWpf/wiki/ProgressRing

I wish that was true, but even the new stuff, like their new frameworks, performs poorly while their older frameworks perform really well. That's brand new code, with no legacy codebase to care for.

The reason why I don't recommend Winui is the million bugs it has. See the github issues page. All Microsoft ui stuff sucks currently. But if you use WPF why not FluentWPF

Development for WinAppSdk and WinUI 3 is also very slow and Microsoft seems to not want to push it and invest more developers into it for some reason. They try to improve the framework, is just it's a small team. For example it was a headacke to apply the Mica backgrop and required unmanaged code, they made it simpler and reduced it to a line of code but it took months. I have 2 out of 7 issues fixed on WinAppSdk repository and 0 out of 8 issues fixed in the WinUI 3 repository (some of the older than a year). This are just my issues, there are many other opened by other developers. So yeah, it wasn't fun at all. PoweshellSDK had an issue with the Import-Module command and it wasn't fixed for more than a year and probably won't be ever fixed, but I'm glad I found a workaround, even more clean and more safe, otherwise I couldn't have added the posibility to uninstall and change Store apps.

Compared to UWP or WPF, WinUI 3 is somewhere between 100-200% slower and consumes 7-20 times as much RAM as the old frameworks (for certain operations).