[ripley12]

I don’t particularly expect WinUI 3 to take off, sadly. I agree that it’s disappointing.

The team still has a lot of work to do; unpackaged applications still aren’t supported, for one. And even once it’s production-ready (next year?), I’m not sure it will be good enough to use instead of web UI.

I do quite like how easy it is to build UIs that work for both keyboard+mouse and touchscreens. But overall it’s basically WPF with a few improvements, and the worst parts of WPF (styling, verbosity) are still there.

[pjmlp]

I wish it was an improvement over WPF, it can hardly match WPF in feature comparisasion, every time someone complains we get the standard reply of getting in touch and explaining our case.

The XAML is incompatible as the rendering engine doesn't expose the same feature set.

Well, our use case is not to rewrite everything yet one more time, a use case that apparently is hard to understand.

Designers aren't supported, yet another please get in touch and explain your business case kind of answer.

[Const-me]

> the worst parts of WPF (styling, verbosity) are still there

WPF is supported in Expression Blend, the tool helps with both styling and verbosity. For optimal UX it needs a bit of support from within the application, to provide design-time data. Ain’t terribly hard to do, and helps a lot when working on WPF GUI apps.

WinUI is not currently supported in Blend.