Repository navigation
🚀 WinUI OSS Update: Phased Rollout Toward Open Collaboration #10700
Replies: 32 comments 179 replies
|
Thank you Beth Pan (@beth-panx) also, Here, we have an excellent list of issues that need to be addressed. |
|
Maybe the first community call back, should answer some fundamental questions after the long silent stagnation of WinUI and WinAppSDK.
|
|
Beth Pan (@beth-panx) Relieved that WinUI is very much alive and also there are people behind it listening. Love WinUI. |
|
This is a great news for me. I love WinUI3, built 2 fully featured apps in the past 8 months with it. Naturally, seeing Microsoft investing in it more and using it in their own apps (recently the Copilot app) is a good sign. |
|
I've been heavily invested in WinUI for years now. I sold it to our organisation as part of our modernisation efforts and we embraced it. To be frank, I don't think Microsoft understands the damage they have caused to the evangelists and wider developer community, along with the companies who have embraced the never-ending stagnation and false promises from WinRT->UWP->WinUI/WASDK. We still don't have a working solution for input validation and basic things like modal dialogs are buggy - how exactly is a LOB application meant to work with such severe limitations? Our company has been building Windows clients since Win3.0. We are not doing any Windows-first development anymore because of the lack of transparency, lack of progress, lack of accountability, lack of direction. WinUI is now ~15 years old if you count its evolution from Win8 (and I suspect parts of it date back to DirectUI in XP) and you're orders of magnitude behind Apple's operating systems. How is it that they can iterate and add new features so quickly and yet WinUI is still riddled with shortcomings and bugs? Martin Anderson (@mdtauk) has raised some great points and I'd love to see answers to all of them. I'll add a few more to the list:
Forgive my cynicism - I hope to see this project succeed but based on what I've seen over the years, I don't have high expectations. |
|
Honestly, this looks like outsourcing whatever is left from WinUI and wish whoever still believes Microsoft is serious about WinUI good luck. You guys never have taken seriously how much the whole tooling and rewrite demands, since Windows 8, have burned all the good will from Windows developer community. There is hardly any reason for a business to invest a new application into WinUI as foundation for their business. It can't even match the features from UWP to this day. |
|
It's time for Microsoft to admit that the entire WinRT (and its follow-on WinUI) idea was a mistake. It has its roots in the Windows 8 fiasco. There were a lot of bad decisions made back then and WinRT was one of them. Like trying to rebuild .NET natively (and differently!) in the OS where .NET languages take a performance hit calling into a foreign ABI and paying for interop costs and losing native .NET performance features. The whole thing was built for language projections and after all this time they only support two languages with WinUI? C++ and C#, neither of which integrate well. The fact that they gave up on adding Rust support for WinUI in a system that was supposed to be designed for such a thing speaks volumes. Just move on from WinRT and WinUI (and put XAML in moth balls too) and give us something like Flutter, Jetpack Compose, or SwiftUI. Something where you don't have to deal with multiple languages to create a UI. |
|
fix the fundamental issues with performance and mouse wheel scrolling that hurts the eyes |
|
Too early to know if we made a mistake, but we are developing a large application in WinUI that connects to MariaDB for the backend using EF Core. The lack of decimal support in XAML binding and in the WinUI controls has been killing us. I know someone was working on decimal support for 1.8, and thank you for that. Will that be in the final 1.8? Will you be able to bind decimal values directly to the existing or a new NumberBox control without using a converter? You said to keep sharing feedback, so I am 😄 And please don't make me feel any worse about choosing WinUI3, it is a great platform, I just wish we had things like decimal support, input validation, window switching that wasn't so buggy, and a designer in Visual Studio. My life would be complete. 😄 |
|
I personally seriously want the Microsoft.UI.Input.dll to be open source. |
|
If we are interested in contributing code to help move this forward is there a process for that? |
I hope that this will also help resolve #2488, in particular where it was mentioned that there are too many breaking changes at the WinUI level. Overall I agree that the priority should be fixing critical issues, however I believe that going towards fully open source can help with this. |
|
Hey everyone – I wanted to share a quick update on WinUI going OSS. Since our announcement, we’ve been making steady progress untangling the codebase from proprietary layers in preparation for both Phase 1 and Phase 2 outlined in the original plan. Because WinUI’s shipping schedule is tied to the Windows App SDK, our branching strategy now lets us start completing PRs alongside the upcoming WASDK 1.8 release. The 1.8 Preview shipped on August 19, and the stable release is coming soon, which gives us the right foundation to begin integrating changes. With that alignment, we’re targeting early October for completion of Phase 1. Phase 2 is still in active development, and while we’re treating it more cautiously, we hope to share tangible progress soon. Thanks again for your patience and continued support. |
This comment was marked as off-topic.
This comment was marked as off-topic.
|
Nice initiative, could you please also release WSA as OSS? |
|
Hey friends! Just want to give a quick update that phase 1 is completed last week. I was OOF, so I wasn't able to provide the update in time. You should see more frequent checkins on winui3/main branch now. We are actively working on phase 2 currently. We aim to get this done in late November. |
|
Hello everyone! As of today, we have completed phase 2 and the winui3/main branch has been merged into main. This means you should be able to build the repo locally. 🥳 Lots and lots of good work from our team especially Mike Crider (@codendone) Alexandre Zollinger Chohfi (@azchohfi) and with the help of reviews from Michael Hawker (@michael-hawker) Chiara Mooney (@chiaramooney)... finally to the best Morten Nielsen (@dotMorten) for early validation. We will now target phase 3 completion by end of February. Thanks for following along and let us know your feedback. |
|
Would WAS allow local-building? I asked this question in the WAS repository before, because I noticed when trying to build it that it relies on private NuGet sources. They told me that since very few people do this, they no longer support this. I know there are still some closed-source components in WAS, but I would like to be able to build the open-source parts myself and also support community contributions. |
|
I'm confused, are you using |
|
This is all great, but with news like this: https://www.windowscentral.com/microsoft/windows-11/windows-11-will-finally-get-its-missing-agenda-view-but-microsoft-rebuilt-it-in-the-worst-way, I am losing hope little by little. If the Windows team itself is favoring JS and HTML to WinUI for its own Shell, why on Earth would any developer invest his time in WinUI? Beth Pan (@beth-panx) , a penny for your thoughts? |
|
Dare I ask, where is this at? Another change in leadership? |
|
|
Currently, it is not possible to compile the MSIX package and XAML compiler. I would like to know what the priority of these two points is? I hope to improve them as soon as possible. |
|
It's April now, what's going on? |
|
Hey everyone — quick status update: We’ve successfully completed Phase 3, and the tests are now available for you to explore. The team is currently working on Phase 4, which will focus on enabling development in GitHub next. Due to the complexity of the XAML compiler codebase, we don’t have a precise timeline to share just yet. We want to do this right by modernizing the compiler code, so it's open-sourced properly. We’ll provide an update on timing as soon as we have a clearer estimate. In the meantime, we’re also continuing to open up documentation that was previously internal-only. You can find instructions on how to run the tests here. Thanks as always for your engagement and feedback! |
|
Phase 4 update: WinUI development is now happening on GitHub Hey everyone! We have a big milestone to share on the road to community contributions. Mainline WinUI development is now taking place on GitHub. WinUI engineers and other Microsoft developers are creating branches, opening pull requests, reviewing, validating, and merging changes right here in this repository. Our day-to-day engineering work now happens in the open, so you can follow progress as it happens instead of waiting for changes to land. At this stage, pull requests are coming from Microsoft developers. We're using this period to prove out the contribution workflows, validation, documentation, and release processes end to end. The goal is simple: when community pull requests open up, contributors should have a pipeline that's reliable and predictable. We'd rather earn that than rush it, and the team is working toward it. We'll keep working through the broader OSS goals shared in this thread and will post here as the next set of milestones takes shape, including an update when we're ready to accept contributions from the community. Thanks as always for your engagement, patience, and support! ❤️ |
|
I hope that the XamlCompiler can truly become open source and allow community contributions. The XamlCompiler has some bugs that have remained unfixed for a long time, and enabling WinUI to embrace C++ modules requires support from the XamlCompiler. Compilation speed and memory usage during compilation have always been pain points for C++, and modules have already been proven to significantly improve this issue. WinUI 3 has been proven to work with C++ modules (see the links below) though it requires some ugly workarounds, which is the part that the XamlCompiler needs to improve. https://github.com/microsoft/cppwinrt/blob/master/nuget/modules.md |
My Experience of using WINUI 3 for Several YearsAfter several decades of developing LoB systems with a range of technologies> I decided to rewrite an application which my business partner and I developed at the turn of the century. It was developed in VB6 using SQL Server 7 and that was my only prior experience of Windows development tools to develop a serious system. The goal was to produce a the new application using Microsoft Technologies with no commercial third party software requirements. I eventually landed upon Project Reunion and started to investigate. Shortly after, Project Reunion was released as WINUI 3 and following some prototyping I decided to go with it along with MVVM, SQL Server, Entity Framework and MVVM + DI. It's been quite a journey, sometime lonely, sometimes anxious: wondering whether WINUI 3 was the right choice. The initial goal has been largely achieved and I can tell you that the application is fully featured and better than anything I have ever worked on. If you are looking for a solid modern Windows development platform here's a positive message for you. There is nothing I haven't been able to do albeit there are pitfalls and there are some weak areas. I found this book a good help early on: ISBN 978-1-80323-566-0. More recently Copilot has been invaluable. I didn't have a XAML point of reference such as UWP or WPF, but then I also didn't have the baggage of legacy UWP or WPF code and experience. I see the same issues reported all the time.
The app currently uses legacy WCT Datagrid - it has some shortcomings, they can be worked around, but it isn't as fluent as a native WINUI control. It may be wise to investigate an alternative, or wait until Microsoft develops a new Datagrid. Copilot assures me this is a "definite commitment" - please let that be true (we shouldn't have to beg :) !! The "missing pieces" I've encountered were addressed with the following.
|
|
ci-cd (@Christopher-Ingram) |
|
Love the news, but please address the loss of mouse behavior that happens sometimes - seems to be related to RDP use - #10009 (comment) |





Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Status updated on August 28th, 2026: (✅ - Done | ⌛ - In Progress | ⏭️ - Planned)
Hey everyone,
Thanks for all the feedback, questions, and ideas. We hear you loud and clear and are taking it seriously. We're entering a new phase of focused improvements over the next 6 months, including product work and foundational changes to support a more open and collaborative future.
Many of you have asked about truly open sourcing the repo. While we’re not ready to commit to a specific end date for completing all milestones, we are actively working toward it. This isn’t a flip-the-switch moment, it’s a deliberate process.
📆 Phased Rollout Plan
We are taking a phased approach to opening up the repo:
Phase 1: Increased Mirror Frequency ✅
After the WASDK 1.8 release (end of August), we’ll begin more frequent mirroring of internal commits to GitHub to increase transparency and show progress.
Phase 2: 3rd Party Devs Build Locally ✅
External developers will be able to clone and build the repo locally, with documentation to guide setup and dependencies.
Phase 3: 3rd Party Devs Run Tests ✅
We’re working to untangle private dependencies and make test infrastructure publicly accessible.
Phase 4: GitHub as Center of Gravity ✅
GitHub becomes the primary place for development, issue tracking, and community engagement. Internal mirrors will be phased out.
Next steps: Governance & Contribution ⌛
🧱 Why It’s Complex
WinUI has deep roots in Windows. Parts of the codebase touch proprietary layers that can’t be published as-is. We’re working to separate what can be shared from what can’t. This work is in progress and takes time.
🎯 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.
💡 How You Can Help
If you’re passionate about WinUI 3 and want to contribute:
We are working on making incremental progress and will share more soon. We will start using this project board to work collaboratively with the community on product prioritization. We also commit to better wiki and transparency on monthly planning. We know this isn’t everything you want to hear, but we hope it shows we’re serious about doing this right. We’ll keep sharing updates as we go.
Thanks for sticking with us 💙
All reactions