Having used Windows App SDK extensively, I tend to agree. It’s got a ways to go and its support for traditional unpackaged/win32 apps is just not there yet.
Also I should note that WinUI 3 is separate from Windows App SDK so it can theoretically become the standard UI kit for other Windows dev approaches as well but it’s still early.
Comments
If you want it to be “native” on Windows then the Windows backend should use controls from Windows App SDK, not GDI.
As someone that spends most of my development life on Windows, I wouldn't bet anything on WinAppSDK until the likes of Office or VS make use of it.
Right now its future is as certain as UWP.
Having used Windows App SDK extensively, I tend to agree. It’s got a ways to go and its support for traditional unpackaged/win32 apps is just not there yet.
Also I should note that WinUI 3 is separate from Windows App SDK so it can theoretically become the standard UI kit for other Windows dev approaches as well but it’s still early.
What? Why? Do you expect support for Windows’ original API to be dropped soon?
Nah, maybe they are an agent of WinUI 3.0 team in disguise. :)
Still plenty of catch up with Win32 to do, when adding up all issues across WinUI, WinAppSDK, CsWinRT, C++/WinRT and new kid in town, Rust/WinRT.
Assuming they don't reboot the whole teams yet again by next BUILD.
The “native” controls of Windows 11 use WinUI. The Settings app demos most of them.