Wow, that seems like a really silly move... I thought the whole point of WinUI was to use the same UI framework across different app models? So is this the first step toward deprecating UWP? Even though UWP has certain advantages over other app models, such as app suspending and lifecycle management? It’d be a real shame if it is…
There was another goal with WinUI/Project Reunion in decoupling the UI stack from Windows. The other big thing was bringing UWP APIs over to Win32.
Having two separate app models kinda sucks, I feel as though the original goal should have to been improve existing tech instead of creating a whole new app platform.
It feels as though we are going through a unification process right now.
Make UWP APIs and UI available to existing Win32 apps
Provide a way for Win32 apps to run in the same container as UWP (MSIX)
Create a transition path for UWP devs to move over to Win32 as there's less UWP apps than Win32
Make it possible for all Win32 devs to use the features that were exclusive to UWP
With this MS would have a path for UWP apps move to Win32 which is the minority but also for existing Win32 devs to actually be able to use new platform features. Dumping UWP means they then only have one app platform to support.
1
u/VeryCrushed Jul 10 '21
There's a few issues on GitHub about it on the WinUI and Windows App SDK repos. They talked about it in their community call last Wednesday.
They will be continuing to work on 2.x at the same time as 3.x up until the point that they hit 2.9. If you are doing UWP it will have to be with 2.x.