I am worried about the future of native UI technologies on Windows. Traditionally at least the developers of operating systems have eaten their own dogfood and have at least tried to implement well-performing & visually consistent native applications to serve as an example to others. Windows 11 has largely done the opposite. Windows has had minimal but perfectly functional native email and calendar apps at least since Windows 10 (could have been in 8, never used that). Windows 11 originally shipped with those apps, but they were removed in a later update and replaced with laggy webview wrappers that take seconds to start.

> Alignment with Microsoft Goals

> We are being thoughtful about resourcing. This effort is happening alongside other critical responsibilities like security, platform stability, and support for existing products. Our current focus is on foundational work that unlocks value for contributors and increase transparency. We are aligning this work with Microsoft’s broader business priorities to ensure long-term support and impact.

I don't sense any benevolence in their words. They are just pulling off their resources and dumping the framework on the public, hoping passionate losers will contribute.

No one in Windows development community cares about WinUI, other than those with sunken costs that bought into the WinRT/UWP dream and now are stuck with a dead technology.

Too many burned bridges since Windows 8 came out.

If anything, this is Microsoft confirmation that they are unwilling to fix all the broken issues, and hoping the community will somehow still care.

I already lost count how many UI frameworks are in windows. It looks like complete chaos and mess.

I really wonder what they expect from open-sourcing it. Just to pretend how open they are? Or is there any real benefit to developers who target windows?

I kind of wish Microsoft would just continue development of WPF. I've used it for years for various projects, and there is a learning curve but I've since enjoyed working with it. XAML, data bindings, ViewModels... all of it I actually like. But, WPF needs a few improvements to really make it perfect. I tried several of Microsoft's newer frameworks and the open source ones (Avalonia, Uno), but I either couldn't get the sample projects to even build successfully on my machine, or I never got comfortable with development workflow, and went back to what I know.

My big idea to fix WPF is to rebuild the data binding system to use the .NET compile-time code generation feature instead of run-time reflection. I think that would solve a lot of problems. For one, projects could do an actual AOT build of their applications (right now, you either need to rely on an installed .NET runtime or "publish" the project with a lot of .NET libraries included for self-extract, bloating the final file size). Code generation would probably improve performance quite a bit too, maybe open up the possibility to compile for cross-platform, introduce type safety for XAML bindings (rather than getting vague runtime binding errors), remove the need for so much class scaffolding, etc... I've thought about starting an open source project to do it myself, but seems like a pretty big task and I would essentially be starting a project to help with my other project which I already don't have enough time to work on...

Meanwhile a single developer makes performant native UIs in his first native program by actually learning how the OS and winapi work

https://m.youtube.com/watch?v=bUOOaXf9qIM

Last I evaluated it WinUI3 was a terrible developer experience. The application had to be literally installed on the system to even debug it, which means you end up with a large number of useless start menu entries, not to mention registry entries and such. Another thing was that the example programs crashed when I clicked on a button.

All I want is something simple to work with to make applications for Windows, and so far I'm still using Win32 with WTL.

For Windows UIs I've been getting into Win32/GDI/DirectDraw/etc.

Tools like CsWin32 and modern C# (ref returns) make working with these APIs a lot more approachable today. It used to be the case that you had to create a nasty C++ project to do any of this. Now you can just list the methods you need access to in your nativemethods.txt file and the codegen takes care of the rest.

Win32 is a lot lower level than other things you'd typically consider to be a "UI framework", but the important tradeoff is that it is also a lot harder for Microsoft to remove or screw with in any meaningful way. I cannot come up with something that has been more stable than these APIs. The web doesn't even come close if we are looking at the same timescales.

As someone reading the comments here and never made a real Windows app outside of a visual basic hello world a pretty long time ago. Why doesn't Microsoft just stop making these? They already own GitHub and vscode so why not just admit that electron/typescript is the Windows UI framework now?

I hope this leads to having a native vertical taskbar, which has been absent in W11 despite being a taskbar feature dating back as early as Windows 98.

Third-party tools have tried to reimplement it but it's either been by bastardizing the native W11 horizontal taskbar to be vertical (eg: Windhawk) or just restoring the old W10 taskbar code (eg: StartAllBack).

I won’t benefit from this. At the same time, I cannot see a single bad thing about it, so I’m surprised about all the negative energy.

I wonder how much longer Microsoft stays committed to Windows as a whole. Windows is less than 10% of the company, users are migrating to phones, tablets, and Chromebooks (all of which can run Office), and with .NET on Linux, Windows servers are making less sense. It's a shrinking market.

If only they'd open source Windows Explorer and the taskbar/start menu, rather than resisting peoples attempts to customise them through other hackery.

So, they gonna abandon it soon?

Even for Windows-only GUI software, it is much safer and sane to use cross-platform frameworks such as wxWidgets and Qt Widgets.

Actual - and rather different - title (as borne out by reading the article):

Microsoft is taking steps to open-sourcing Windows 11 user interface framework

They need to feed it to all the LLMs to get help keeping it from falling apart.

They could go back to Win32 + WinForms and everything would be fine.

Confused, the Win 11 UI framework, Electron, is already open source.

Dumb question from somebody who doesn’t do gui stuff: is this like a Window Manager, or more like GTK or QT or whatever?

Could microsoft still build windows today?

"We laid off most of the team despite record profits and need free labor to maintain what remains"

Seasons may come and go, but one thing will never change.

Windows and an absolutely baffling array of UI frameworks with various pitfalls, uncertain futures, and no clear winners.

(honorable mention to WinForms though.)

I really hope they do and the rendering engine is decently decoupled, I'll give a try building a framework on top of it.

I wish all platforms gave access to their rendering engine similar to DOM on the web, imo SwiftUI/WinUI (or WPF, but they are very similar) are not that good.

Haven't built anything native on Linux, though, no idea how good those are.

Does this mean that we will be able to get the Quicklaunch toolbar back?

What we wanted: Win7 UI open source

What we got: Win11 dumpster fire, free for everyone to fix

How was it implemented? C#? C++?

Microsoft has a long history of releasing numerous UI frameworks: VB, MFC, WTL, Silverlight, WPF, WinForms, and others. Yet despite this abundance, many of the core components Microsoft used in its own applications were never available to developers. They rarely ate their own dog food, and desktop UI development relied on third party components. For the past two decades, native desktop UIs have steadily declined in favor of web-based components, so it's unclear what the real benefit of another native framework would be today.

I'm sure it'll be really user friendly(!)

So will we be able to have more than 11 programs on the taskbar without them being compacted?

Or a 2 row taskbar?

So I can easily switch between my 40 windows open? What is good for productivity?

What "UI framework"? Windows is a Frankenstein's monster of different UI elements.

open-sourcing it so they can get free labor.

winui3 was abandoned the moment it was conceived.