Microsoft is taking significant strides to enhance the user experience of WinUI 3 applications on Windows 11 by addressing the long-standing issue of black tearing during window resizing. This initiative is part of the company’s broader commitment to rejuvenate native app development on its latest operating system.
The transition to Windows 11 has been marked by a complex amalgamation of legacy interface elements and modern applications, leading to a somewhat disjointed user experience. Among the most noticeable visual bugs has been the black tearing that occurs when resizing WinUI 3 apps. Fortunately, March Rogers, Microsoft’s Partner Director of Design, has confirmed that a solution is in the works, with a rollout expected to begin this summer.
“We are working on platform improvements to solve the tearing…. Will start rolling out over the summer,” Rogers stated, offering a glimmer of hope to developers and users alike who have been grappling with this issue. The anticipation builds as it becomes clear that the majority of built-in Windows 11 applications are based on the Universal Windows Platform (UWP), which already enjoys smooth resizing capabilities. For instance, the Clock app, a UWP application, exemplifies this seamless experience, contrasting sharply with the Photos app, which suffers from the aforementioned tearing due to its WinUI 3 foundation.
Smooth resizing is coming to WinUI 3 apps this summer
A recent inquiry from a developer on X prompted a response from the Windows design and engineering leads regarding the need for WinUI 3 apps to achieve the same level of smooth resizing as their UWP counterparts. The developer highlighted that legacy UWP applications, such as the Microsoft Store and Windows Clock, resize without issue, while modern WinUI 3 applications face significant visual glitches during this process.
Rogers indicated that the Windows team is currently testing the smooth resizing code on native inbox applications to ensure stability before extending the update to the Windows App SDK. This proactive approach not only aims to resolve the tearing issue but also hints at the potential for more native first-party WinUI 3 applications in the near future. Notably, Rudy Huyn, a Partner Architect at Microsoft, has been assembling a team dedicated to developing entirely WinUI 3 applications for Windows 11.
Despite the excitement surrounding these developments, it raises questions about the disparity in performance between UWP and WinUI 3 applications, especially considering that UWP has been officially phased out by Microsoft.
The struggle to replace decades of legacy desktop code
The challenge of modernizing Windows 11 is compounded by its reliance on the Win32 framework, which has been in place for over three decades. This legacy codebase presents significant hurdles when attempting to implement a modern, GPU-accelerated user interface. The internal design teams at Microsoft are acutely aware of these graphical inconsistencies and are focusing on enhancing the design of Windows 11, starting with the Settings app to eventually replace the outdated Control Panel.
However, the task of untangling this complex web of legacy code is monumental. Microsoft has previously explained the difficulties in fully retiring the Control Panel due to entrenched enterprise dependencies and intricate registry keys that cannot be rewritten without risking the stability of essential administrative tools. This slow migration results in a user experience that juxtaposes modern design elements with outdated dialogue boxes, a situation that is further complicated by the presence of remnants from Windows 8.
Native WinUI 3 applications are replacing sluggish web wrappers
In response to these challenges, Microsoft is doubling down on WinUI 3 to combat the proliferation of cumbersome web applications that have plagued the operating system. The company is pivoting away from heavy frameworks like React Native and WebView2, which have drawn criticism for their inefficiency.
One of the most fundamental components, the Start menu, is set to transition from web-based React components to WinUI 3, marking a significant step towards a more cohesive native experience. Additionally, system-level dialog boxes are undergoing substantial upgrades, with the new Windows 11 Run dialog demonstrating the superior performance of modern C# and WinUI 3 frameworks compared to their Win32 predecessors.
As the momentum builds across the Windows shell interface, even the legacy File Explorer properties dialog is slated for replacement with a WinUI 3 version, complete with dark mode support. However, the real challenge lies in convincing third-party developers to embrace native app development for Windows 11.
Rebuilding third-party developer trust with Windows App SDK 2.0
For Windows 11 to thrive, it is crucial that third-party developers adopt WinUI 3. Currently, the desktop ecosystem is struggling, with even Microsoft downgrading its Copilot feature to a sluggish web app. A recent report highlighted the reasons behind the prevalence of web apps over native ones, pointing to Microsoft’s inconsistent commitment to a single framework and the historical challenges associated with the Windows App SDK.
Developers have often encountered bugs and a lack of essential visual features, such as smooth resizing, which diminishes their incentive to utilize native code. In contrast, macOS continues to benefit from highly optimized native applications, thanks to its seamless UI frameworks.
In an effort to shift this narrative, Microsoft has launched Windows App SDK 2.0, which reflects the company’s attentiveness to developer feedback. This new release introduces enhanced XAML capabilities, modernized Storage Pickers, semantic versioning, and expanded popup anchoring APIs, all designed to simplify the development of beautiful native Windows software.
With the upcoming summer rollout of smooth window resizing and the introduction of hardware-level CPU enhancements, the future of Windows 11 appears promising. Microsoft’s renewed focus on native WinUI 3 code is a crucial step towards restoring a sense of premium quality to the Windows platform, moving away from the inefficiencies of the web app era.
