Microsoft is taking significant strides to enhance the user experience of WinUI 3 applications, particularly addressing the long-standing issue of black tearing that occurs during window resizing. As the company aims to rejuvenate native app development within the Windows 11 ecosystem, users can look forward to a smoother resizing experience akin to that of Universal Windows Platform (UWP) apps.
The transition to Windows 11 has been marked by a complex interplay of legacy interface elements, sluggish web wrappers, and modern native applications. Among these challenges, the visual glitch of black tearing during the resizing of WinUI 3 apps has been particularly frustrating for developers and users alike. Fortunately, March Rogers, Microsoft’s Partner Director of Design, has confirmed that a fix is in the works, with plans to roll it out in the near future.
“We are working on platform improvements to solve the tearing….Will start rolling out over the summer,” Rogers stated, providing reassurance to those who have experienced this issue.
Interestingly, many users may not have realized that WinUI 3 apps lacked smooth resizing capabilities, as the majority of built-in Windows 11 applications are UWP. For instance, the Clock app, a UWP application, showcases seamless resizing, while the Photos app, built on WinUI 3, suffers from noticeable tearing during resizing.
Smooth resizing is coming to WinUI 3 apps this summer
A recent inquiry from a developer on X prompted discussions among Windows design and engineering leads regarding the need for WinUI 3 apps to achieve the same smooth resizing that legacy UWP applications enjoy. The developer highlighted that while applications like the Microsoft Store and Windows Clock resize flawlessly, modern WinUI 3 applications often display severe visual glitches, resulting in unsightly black borders during resizing.
In response, Rogers confirmed that the Windows team is actively working on platform improvements to rectify the tearing issue. Currently, the team is testing the smooth resizing code on native inbox apps to ensure stability before it is rolled out to the Windows App SDK. The anticipated rollout is set to commence over the summer, a development that brings relief to both power users and developers.
Moreover, Rogers’ mention of testing on inbox apps hints at the potential for more native first-party WinUI 3 applications in the future. This aligns with previous reports indicating that Rudy Huyn, a Partner Architect at Microsoft, is leading efforts to develop 100% WinUI 3 applications for Windows 11. Recently, David Fowler, a distinguished Engineer at Microsoft, expressed enthusiasm on X, stating, “Native apps are BACK!”
Despite the excitement surrounding these developments, it is intriguing to note that UWP applications, despite being officially abandoned by Microsoft, continue to offer a smoother resizing experience compared to their WinUI 3 counterparts.
The struggle to replace decades of legacy desktop code
Microsoft’s journey with Win32 has proven to be a double-edged sword. Initially, the company did not anticipate the longevity of this legacy code, yet Windows 11 remains built upon it. The challenge of integrating a modern, GPU-accelerated user interface framework over three decades of legacy code has led to significant rendering issues.
Microsoft’s internal design teams are acutely aware of these graphical inconsistencies. Recently, the company has shifted its focus to enhancing Windows 11’s design, starting with the Settings app to replace the outdated Control Panel. Rogers and his team are diligently addressing graphical bugs to create a cohesive desktop experience. However, untangling the complexities of legacy code remains a monumental task, with deeply embedded enterprise dependencies and intricate registry keys complicating the process.
This gradual migration has resulted in a disjointed user experience, where modern design elements coexist with outdated dialogue boxes. Additionally, remnants from Windows 8 persist, though Microsoft has confirmed plans to replace these old UI elements in Windows 11.
Native WinUI 3 applications are replacing sluggish web wrappers
In light of these challenges, Microsoft is intensifying its commitment to WinUI 3, aiming to liberate the operating system from the burden of bloated web applications. After facing criticism, the company is pivoting away from heavy React Native and WebView2 architectures.
It is unfortunate that fundamental components like the Start menu have not yet transitioned to native code. However, Microsoft has announced plans to migrate the Windows 11 Start menu to WinUI 3, moving away from web-based React components. System-level dialog boxes are also undergoing significant upgrades, with the new Windows 11 Run dialog demonstrating the superior performance of modern C# and WinUI 3 frameworks compared to older Win32 code.
The momentum continues to build across the entire shell interface, with the legacy File Explorer properties dialog set to be replaced by a WinUI 3 version, complete with dark mode support. While these advancements are promising, the key challenge remains in persuading developers to create native applications for Windows 11.
Rebuilding third-party developer trust with Windows App SDK 2.0
For Windows 11 to thrive as a platform, it is essential for third-party developers to embrace WinUI 3. Currently, the desktop ecosystem is facing challenges, with even Microsoft downgrading Copilot to a sluggish web app, although a redesign is on the horizon.
A recent report highlighted a developer’s perspective on why Windows 11 continues to see a prevalence of web apps over native applications. The root of the issue lies in Microsoft’s historical inconsistency in committing to a single framework. The Windows App SDK has been plagued by bugs and usability issues, lacking essential visual features like smooth resizing. Consequently, developers often opt for Electron or WebView2 to ensure consistent visual quality, especially when faced with the black tearing issue.
In contrast, macOS has consistently delivered highly optimized native applications, thanks to its reliable UI frameworks. Microsoft is actively working to change this narrative. The recent launch of Windows App SDK 2.0 reflects the company’s responsiveness to developer feedback, introducing new XAML capabilities, modernized Storage Pickers, semantic versioning, and expanded popup anchoring APIs.
Additionally, Microsoft is simplifying the process of building aesthetically pleasing native Windows software through robust command-line tools.
<figure id="attachment89799″ aria-describedby=”caption-attachment-89799″ class=”wp-caption aligncenter”><figcaption id="caption-attachment89799″ class=”wp-caption-text”>TabView template using Command-Line. Source: Microsoft Dev Blogs
This refined developer toolkit, coupled with the upcoming summer release of smooth window resizing, paints a promising picture for the future of Windows 11. Furthermore, the hardware-level CPU enhancements introduced by the new Low Latency Mode in the May optional update are set to make native applications feel even faster upon launch. While the era of web apps has posed challenges for desktop efficiency, Microsoft’s renewed commitment to native WinUI 3 code is precisely what the Windows platform needs to regain its premium feel.