Microsoft is requesting developers to create 100% native Windows applications to improve system performance. Rudy Huyn, a Partner Architect at the company, recently made this appeal on X. The goal involves replacing memory-intensive web-based programs with optimized software that runs directly on the operating system.
Key Details
This initiative marks a significant shift away from the previous assumption that everything would eventually become a web app. Huyn specified that the new applications must use WinUI without WebView content underneath the interface. WebView acts as a mini browser that often runs Chromium instances in the background of the application.
"100% native," Huyn said when queried over the specific nature of those apps. This distinction implies apps built specifically for the Windows operating system rather than wrapped web content. Many current Windows apps, including parts of the Settings menu, actually run on WebView.
The move addresses significant performance issues associated with current web-based alternatives used by many users. Running a WebView two app requires spooling up a Chromium browser instance behind the scenes. This process consumes substantially more memory compared to traditional native applications.
What This Means
Some users report that loading the WhatsApp login screen with the WebView version soaks up 300 MB of RAM. In contrast, the old native app used under 20 MB of memory during the same operation. With the new version running, it can consume multiple gigabytes, while the native version remains under 300 MB. This discrepancy highlights the inefficiency of running browser engines for simple tasks.
This strategy follows a broader public push from Microsoft to improve the fundamentals of Windows 11. The company is working on reducing disruption from Windows Update and making the taskbar more configurable for users. They are also removing the need to log in online via a Microsoft account during new installs. These changes aim to streamline the user experience without adding unnecessary complexity.
Former Windows development lead Mikhail Parakhin previously worked on a so-called 20/20 project internally. This initiative aimed to reduce both the Windows install size and idle memory consumption by 20%. Microsoft has not committed to those targets publicly but aims to lower the baseline memory footprint. Parakhin's comments suggest this effort has been ongoing for some time.
Shifting as much app code as possible from WebView to native would certainly help with that goal significantly. All in all, this seems like yet another indication that Microsoft has now got its priorities right with Windows. The focus is moving away from AI frills and features toward the nuts and bolts of the OS. Developers will need to adapt their coding practices to meet these new architectural standards.
