Yesterday I made a post (Great News: All Bugs Will be Fixed In the Year 2041) which was meant to be a somewhat funny complaint about the lack of activity in terms of development progress and dealing with user issues submitted here.
Then I made a comparison of activity between WinUI3 and MAUI and those figures are quite revealing when thinking about it:
How can it be possible that MS is investing 20 times more effort into MAUI than into WinUI3 - the new and designated primary UI technology for Windows desktop?
Simple answer: It can't. It can only be possible in case when WinUI3 is no longer the "designated primary UI technology for Windows desktop".
Now I'm shocked to realize that it's way more serious than I thought as so many details suddenly fit together and make sense when being viewed in the light of that premise.
It all fits together
Smaller Bits
- No substantial official statements or responses are being made on GitHub anymore
- The Product Board is outdated and no longer maintained
- The hard drop of WinUI2 support wouldn't have been needed when still working in WinUI3, because large parts of WinUI2/3 code are identical, so certain fixes to WinUI3 could have easily been applied to WinUI2.
- The whole architecture behind this is ridiculously complex, all the projections, WinRT, the insane build system for the WinUI3 code, etc.
- Experience is so inferior compared to .net based implementations - for both, framework consumers and developers
- Inability to ship a visual designer (surely also due to the aforementioned)
- limitations in the composition architecture (no external content overlay)
- Adoption from component vendors hasn't been great
Xbox Development
- No announcement has been made regarding the future of Xbox development
- UWP is dead
- WinUI2 declared as unsupported from one day to another
- WinUI3 doesn't work on Xbox
=> but Xbox is not dead. So the must be something for Xbox which is not WinUI3
Component Vendors
DevExpress are offering a few free components but these haven't been updated since mid-2022.
Their blog entries about WinUI3 stopped in mid-2022 as well (https://search.devexpress.com/?m=Web&q=winui3)
They probably know already about the end of WinUI3.
Timely Coincidence
Wasn't it at the same time (2022) that WinUI3 development had started to be driven down?
XAML Islands as a WinUI3 Exit Strategy
When looking at the changes that were made during the past year, then there's only one area where significant work has been put into: XAML Islands. Even though it had been requested by users earlier, it's not a most-wanted feature, but still, MS picked exactly that part as the one major subject of work.
XAML Islands allows to integrate WinUI3 content as "islands" when using other UI frameworks. Why is this so important? Who needs this other than a few with very specific use cases?
When customers want to modernize their applications, who would start by implementing something in WinUI3 which is then shown like a control/window within a WPF or WinForms app? Normally, such migrations would rather go the other way round: starting with a new application framework and subsequently migrating legacy components. But that's what is not being worked: There's nothing like a hWnd-Panel (which had also been requested by users).
Bottom line: When establishing a new framework for app development, then it's usually crucial to provide ways for developers to integrate legacy components into the new framewrok to allow subsequent migration, but not the other way round. Provisioning for the other direction only (and also as the only major change) can only mean that this is the end of the road for WinUI3, and XAML Islands are just implemented to soften the impact for affected developers enabling a life-after-death existence for WinUI3 components.
MS, when did you plan to make the RIP announcement?
And what will be the replacement?
Yesterday I made a post (Great News: All Bugs Will be Fixed In the Year 2041) which was meant to be a somewhat funny complaint about the lack of activity in terms of development progress and dealing with user issues submitted here.
Then I made a comparison of activity between WinUI3 and MAUI and those figures are quite revealing when thinking about it:
How can it be possible that MS is investing 20 times more effort into MAUI than into WinUI3 - the new and designated primary UI technology for Windows desktop?
Simple answer: It can't. It can only be possible in case when WinUI3 is no longer the "designated primary UI technology for Windows desktop".
Now I'm shocked to realize that it's way more serious than I thought as so many details suddenly fit together and make sense when being viewed in the light of that premise.
It all fits together
Smaller Bits
Xbox Development
=> but Xbox is not dead. So the must be something for Xbox which is not WinUI3
Component Vendors
DevExpress are offering a few free components but these haven't been updated since mid-2022.
Their blog entries about WinUI3 stopped in mid-2022 as well (https://search.devexpress.com/?m=Web&q=winui3)
They probably know already about the end of WinUI3.
Timely Coincidence
Wasn't it at the same time (2022) that WinUI3 development had started to be driven down?
XAML Islands as a WinUI3 Exit Strategy
When looking at the changes that were made during the past year, then there's only one area where significant work has been put into: XAML Islands. Even though it had been requested by users earlier, it's not a most-wanted feature, but still, MS picked exactly that part as the one major subject of work.
XAML Islands allows to integrate WinUI3 content as "islands" when using other UI frameworks. Why is this so important? Who needs this other than a few with very specific use cases?
When customers want to modernize their applications, who would start by implementing something in WinUI3 which is then shown like a control/window within a WPF or WinForms app? Normally, such migrations would rather go the other way round: starting with a new application framework and subsequently migrating legacy components. But that's what is not being worked: There's nothing like a hWnd-Panel (which had also been requested by users).
Bottom line: When establishing a new framework for app development, then it's usually crucial to provide ways for developers to integrate legacy components into the new framewrok to allow subsequent migration, but not the other way round. Provisioning for the other direction only (and also as the only major change) can only mean that this is the end of the road for WinUI3, and XAML Islands are just implemented to soften the impact for affected developers enabling a life-after-death existence for WinUI3 components.
MS, when did you plan to make the RIP announcement?
And what will be the replacement?