Just a few (few) years in the past, Microsoft offered the ‘common apps’ or UWP (Common Home windows Platform) as the future of software development for Home windows. The corporate was then immersed in a strategy of convergence between your PC and cellular working programs, and UWP was going to be the axis on which it rotated.
So satisfied had been they themselves of it that for a time they even they vetoed the presence of Win32 applications (the ‘conventional’) within the Microsoft Retailer.
Nevertheless, everyone knows what occurred to Home windows smartphones. That, coupled with its relative irrelevance among the many developer neighborhood, the next failure of Home windows eight and the rise of PWA applications (noted as their natural successors) they ushered within the decline of UWPs.
Those that wager on UWPs are left within the lurch
And now, lastly, per week after the official presentation of Home windows 11, Microsoft has warned, in one of their ‘WinUI Community Calls’, about what haven’t any plans to replace the Common Home windows Platform to assist WinUI 3.
The session started with a fast definition of phrases by Ana Wishnoff (Microsoft program supervisor), to clear up the complicated state of affairs of the person interface frameworks on Home windows:
“WinUI is the native person interface platform for Home windows 10 and Home windows 11. […] WinUI 2 is the second technology of the native UX stack in Home windows and is designed for UWP purposes. “
“WinUI Three is a brand new third technology of the native Home windows UX stack – it consolidates UX applied sciences beforehand constructed into Home windows right into a single decoupled framework that’s included as a part of the Home windows App SDK (previously referred to as Undertaking Reunion).”
That minority of builders who, as an alternative of betting on reluctance towards UWPs, selected to get on the Microsoft boat, now see how the work invested in growing these purposes based mostly on WinUI 2 will end in obstacles when migrating to the brand new framework.
For many who believed Microsoft’s guarantees, it has been costly: now the winds are blowing in favor of those that stated ‘no’ to UWP, and the corporate leaves them within the lurch
And it’s that, for instance, the identical number of XAML (XML language used within the definition of the design of the apps) is totally different between each variations. And staying on WinUI 2 would not appear to be the best choice as soon as you understand that not appropriate with .NET 5.zero or WebView2 controls.
WinUI program supervisor Ryan Demopoulos clarified in the neighborhood name chat that, regardless of earlier guarantees in that sense, “we have now no plans at the moment to launch WinUI Three for UWP in a secure means”, relatively will develop WinUI 2 and three “in parallel”.
Thus, Microsoft has simply launched WinUI 2.6 and guarantees that, by the tip of this 12 months or early 2022, a WinUI 2.7 can be launched to permit UWP purposes to have affordable assist for Home windows 11. A comfort, in fact, however in the long run issues look dangerous for UWP app builders:
“Our method is predicated on making an attempt to achieve out to the massive present neighborhood of Win32 app builders who haven’t had a great way of accessing the fluid design and most of the controls that WinUI offers.”
By way of | The Register