{"id":126691,"date":"2026-05-13T15:06:49","date_gmt":"2026-05-13T15:06:49","guid":{"rendered":"https:\/\/mailinvest.blog\/index.php\/2026\/05\/13\/microsoft-aims-to-speed-windows-with-leap-forward-in-winui-3-perf\/"},"modified":"2026-05-13T15:07:55","modified_gmt":"2026-05-13T15:07:55","slug":"microsoft-aims-to-speed-windows-with-leap-forward-in-winui-3-perf","status":"publish","type":"post","link":"https:\/\/mailinvest.blog\/index.php\/2026\/05\/13\/microsoft-aims-to-speed-windows-with-leap-forward-in-winui-3-perf\/","title":{"rendered":"Microsoft aims to speed Windows with ‘leap forward’ in WinUI 3 perf"},"content":{"rendered":"

<\/a>\n
<\/p>\n

\n

OSes<\/p>\n

Bittersweet put up tells devs what they already knew: The framework is just too sluggish<\/p>\n<\/div>\n

\n

Microsoft claims to have achieved a “leap ahead” in efficiency for WinUI 3, the present native framework for Home windows apps, with a 25 p.c enchancment for the elements of File Explorer coded utilizing this framework. <\/p>\n

Software program engineer lead Beth Pan posted<\/a>\u00a0figures for the WinUI portion of File Explorer, displaying 41 p.c fewer reminiscence
\nallocations and 45 p.c fewer perform calls. She added that some
\noptimizations “contain small or giant breaking modifications,” so they may
\nbe opt-in at first for builders utilizing the framework. The plan is for the optimizations to turn out to be the default in future variations of WinUI and the Home windows App SDK,
\nwith opt-out accessible when wanted.<\/p>\n

\n
\n

\n WinUI 3 is at the moment measurably slower than each WPF and UWP\u2026 that is NOT OK
\n <\/h3>\n<\/p><\/div>\n<\/div>\n

The brand new optimizations are a part of a push to make Home windows
\nextra responsive. In March, Home windows boss Pavan Davuluri promised<\/a>\u00a0to enhance the standard of the working system, together with a dedication to a “quicker
\nand extra reliable File Explorer.” His put up famous that Microsoft intends
\nto “transfer extra experiences to WinUI 3” for quicker responsiveness.<\/p>\n

Pan’s put up is bittersweet for builders. Efficiency points
\nwith WinUI 3 have been well-known for years.
\nThough Microsoft calls it a local framework, that could be a stretch. WinUI 3 relies on WinRT (Home windows Runtime), a element interface first utilized in Home windows 8 that sits between software code and the underlying Win32 API, which has a greater
\ndeclare to being native. A bonus of WinUI 3 is its help for Fluent UI, the Home windows
\ndesign system. Builders utilizing WinUI 3 get the Home windows 11 feel and look, however
\nnot one of the best efficiency.<\/p>\n

“WinUI 3 is at the moment measurably slower than each WPF
\n[Windows Presentation Foundation] and UWP [Universal Windows Platform]\u2026 this
\nis NOT OK,” stated one comment<\/a>. One other said<\/a>\u00a0that “you may’t construct a WinUI app and name it easy on the similar
\ntime.”<\/p>\n

Part vendor DevExpress has additionally posted<\/a>\u00a0about WinUI 3 efficiency points. The corporate acknowledged that WinUI element structure
\nhas the potential for quick rendering and animation, however that “sadly, every motion inside a element requires
\nWinRT interop, which is sluggish.”<\/p>\n

These issues undermine Davuluri’s hope that utilizing
\nextra WinUI 3 will repair Home windows 11 efficiency, except the framework itself is
\nimproved, as Pan now claims.<\/p>\n

One other longstanding gripe amongst Home windows devs is that Microsoft’s developer division has created frameworks that the Home windows and Workplace groups haven’t all the time adopted persistently. Inside tensions return a few years. Some should keep in mind early builds of “Longhorn,” the code identify for Home windows Vista, having to be reworked earlier than Vista’s eventual launch in 2007 due to efficiency points with .NET.\u00a0This brought on mistrust of .NET within the Home windows group. “What
\nyou could do is definitely use your framework throughout the corporate,” said<\/a>\u00a0one other remark. Pan replied, insisting “that is the push.”<\/p>\n

That is precisely what builders utilizing WinUI 3 wish to hear, however the
\nlengthy and tangled historical past of Home windows UI frameworks suggests {that a} constant and
\nenduring company-wide strategy is unlikely. \u00ae<\/p>\n<\/div>\n