Post

There was an error while loading. Please reload this page .

Our mission is to make WinUI 3 the best native UI platform for Windows experiences and apps and performance is at the heart of that effort. Moving from WinUI 2 to WinUI 3 should always be a clear win for performance, and apps should get great results without heavy lifting.

Pavan recently shared a blog post , in which "more fluid and responsive app interactions: Reducing interaction latency by moving core Windows experiences to the WinUI3 framework" was mentioned as part of our quality commitment. Making this a reality means delivering performance improvements at multiple levels, including within WinUI itself. This also reinforces our strategic commitment to WinUI as the native framework going forward. We know that performance is just one piece of the puzzle and that there are many other areas that deserve our continued attention. Rest assured, we remain focused on those as well.

We've been zeroing in on launch time , using File Explorer and Notepad as our primary benchmarks, with an emphasis on improvements that broadly benefit most apps.

Here's what we're seeing for the WinUI portion of File Explorer launch :

These improvements will be brought out of the development branch soon, and you will see them showing up in the winui3/main branch. We'll also be bringing these changes into WinAppSDK 2.x where possible, though some changes may be too risky or complex to deliver as servicing updates.