When you buy through links on our articles, Future and its syndication partners may earn a commission.
Microsoft’s Shift Towards Native Windows Apps
In a notable pivot, Microsoft is rekindling its commitment to native applications for the Windows operating system. Rudy Huyn, a Partner Architect at Microsoft, recently took to X (formerly Twitter) to rally software developers for a new initiative focused on creating applications that are “100% native.” This assertion signals a clear departure from the trend of relying on web-based applications.
Huyn’s emphasis on “100% native” suggests a future where applications are developed using WinUI without the reliance on WebView content, which has become a common practice. WebView acts as a mini browser within apps, allowing developers to serve web content more efficiently. However, this approach has its drawbacks. Many Windows applications, including components of the Windows operating system itself, have been built on WebView, which can lead to increased memory usage and performance issues.
For instance, the transition of popular applications like WhatsApp to a WebView-based model has raised concerns among users. Reports indicate that the WebView version of WhatsApp consumes significantly more memory than its native counterpart, with some users experiencing memory usage soaring into gigabytes, while the older version typically stayed under 300 MB.
This shift towards native applications aligns with Microsoft’s broader strategy to enhance the foundational aspects of Windows 11. Rather than focusing solely on AI enhancements, the company is prioritizing improvements such as minimizing disruptions from Windows Update, increasing taskbar customization options, and even eliminating the requirement for online Microsoft account logins during new installations.
Interestingly, this initiative echoes insights from former Microsoft Windows development lead Mikhail Parakhin, who previously worked on a project aimed at reducing both the installation size and idle memory consumption of Windows by 20%. Although Microsoft has not publicly committed to specific targets, it has made it clear that lowering the baseline memory footprint of Windows is a key objective. Transitioning app code from WebView to native frameworks could significantly contribute to achieving this goal.
Overall, Microsoft’s renewed focus on native applications suggests a strategic realignment that prioritizes the core functionalities of Windows. As the company shifts its attention away from superficial enhancements, the potential benefits for users—particularly in terms of system memory efficiency—could be substantial, especially in an era where memory costs are on the rise.
