What is the status of WinUI?

[knightmeister]

I hope this is OK to raise this issue here - WinUI is part of the WASDK and the WinUI repository appears to be abandoned. I'm raising this here because the team has not addressed any of the numerous concerns about the state of the project. There has been no communication from the team since the January community call.

microsoft/microsoft-ui-xaml#10520
microsoft/microsoft-ui-xaml#10434
microsoft/microsoft-ui-xaml#9416
microsoft/microsoft-ui-xaml#9417

Is WinUI still under active development by an assigned team?

At this point the WinUI repository is so embarrassing that if it's not going to be actively maintained it should be archived - there are so many issues at this point that are years old - core functionality like input validation.

From my perspective I am getting pressure against using the technology as our clients have concerns about long standing functionality gaps.

[mominshaikhdevs]

and COMv2/WinRT has no other options other than the only WinUI ≥ 3. any other attempts other than the only WinUI ≥ 3, must come to an end.

[HMO-SOUL]

Based on the lastest releases it is still alive but its progress is slow, the current experimental made wasdk into smaller packages to reduce app size
For controls it depends some have bugs others have missing functionalities, but let wait for the next experimental and see what changes they are going to do to WinUI 3
I still have Faith in them despite how disappointing some of the releases were 👍

[knightmeister]

From what I heard, everyone was directly and indirectly involved in the Build conference recently, and the reason for the delays
@ghost1372 I don't get this. There was like 1 build session for WinUI.

[ghost1372]

From what I heard, everyone was directly and indirectly involved in the Build conference recently, and the reason for the delays
@ghost1372 I don't get this. There was like 1 build session for WinUI.

FYI
#5250 (reply in thread)

[whiskhub]

My inofficial assumption is they moved most staff from WinUI to AI, and there's only a small team left that is doing smaller things here and there...

[HMO-SOUL]

@knightmeister
WinUI is partially internal framework, many changes depends on the MS teams that use WinUI 3 for their apps
Still WinUI 1.7 is a great update, what are you missing other than input validation and a datagrid?

[ChenYiLins]

In fact, I think the team should be more committed to improving the performance of WinUI than the function. This doesn't only affect individual developers. Doesn't Microsoft realize that Win11 is ridiculously slow compared to Win10? (Just as Xaml is only partially embedded in Explorer now)

Such as:

• The performance of adding elements in CommandBarFlyout.SecondaryCommands is poor microsoft-ui-xaml#8359 (This affects Win11 desktop and File Explorer)
• Massive lag when dragging a WinUI3 window  microsoft-ui-xaml#9541
• Text rendering performance is embarrassingly bad microsoft-ui-xaml#9565
• ItemsRepeater Memory leak microsoft-ui-xaml#10488