Microsoft is once again refining a critical component of Windows 11: WinUI 3. This framework is the foundation for building modern, native user experiences and applications within Windows, a subject that has faced scrutiny for a while now. As the visual and technical underpinning for various system elements, it’s logical to assume that if WinUI 3 performs better, applications relying on it can launch faster, consume fewer resources, and respond more efficiently. In essence, Windows 11 will see improved performance in this regard, and now we have concrete evidence that this is happening.
The feedback directed at Microsoft appears to be having an effect, albeit gradually. While significant advancements often take time, small steps forward are being made. What we’re about to see is another piece of evidence confirming that this pressure is proving beneficial for Microsoft, following recent developments like the Low Latency Profile.
Microsoft Boosts WinUI 3 Performance in Windows 11, Starting with File Explorer
The most prominent example of these improvements is seen in File Explorer. Microsoft has used File Explorer and Notepad as primary benchmarks to measure launch times, though the published data specifically focuses on the WinUI portion of File Explorer’s startup. This means that the entire File Explorer isn’t necessarily opening 41%, 45%, or 63% faster, but rather these improvements apply to the segment managed by WinUI.
The figures themselves are compelling: Microsoft reports a 41% reduction in memory allocations, a 63% decrease in transient allocations, a 45% drop in function calls, and a 25% reduction in the time spent within WinUI code during File Explorer’s launch. These are substantial gains that promise a smoother user experience.
These numbers are truly impressive, and even though the impact might be subtle at first glance, they offer hope that as these optimizations progress, they will translate into enhanced performance across various parts of Windows 11 that utilize WinUI 3. These are internal metrics, but they are directly indicative of less reserved memory, reduced temporary workload, fewer inter-function calls, and less time consumed by the framework itself.
Microsoft’s Portability Efforts Begin to Pay Off, Much Like Apple’s Approach
Microsoft has been steadily working towards a system architecture reminiscent of Cupertino’s for years, but the company may need to accelerate its efforts following developments like Google’s Aluminium OS and Android 17. This makes WinUI 3 particularly important, as Microsoft is positioning it as the go-to native framework for modern Windows experiences. The company itself explains that transitioning from WinUI 2 to WinUI 3 should result in a clear performance enhancement in Windows 11, allowing applications to achieve better results without requiring extensive modifications from developers.
These advancements will initially roll out from the development branch to `winui3/main`. Microsoft also intends to bring some of these changes to WinAppSDK 2.x where feasible, though it cautions that certain optimizations might be too risky or complex to be distributed as maintenance updates.
There are also caveats to consider. Not every improvement will be straightforward. Some enhancements may introduce breaking changes and require developers to manually enable them. Microsoft points to the optimization of default control styles as an example, which could affect applications that rely on specific templates or properties applied through animations.
With these developments, Windows 11 is not just receiving a vague Microsoft promise of “more fluidity,” but rather measured data pertaining to one of its key visual layers. The next step is to observe how these improvements manifest in real-world usage beyond controlled benchmarks, impacting the daily experience of File Explorer, Notepad, and other native WinUI 3-based applications.
