WhatsApp for Windows 11 Transitions to Chromium Web Wrapper from UWP/Native App

In a surprising move, Meta (now Meta AI) has revealed that WhatsApp is transitioning from its UWP (WinUI) framework to a Chromium-based container on Windows 11. This shift marks a return to the application’s previous structure, although it introduces some updated features, as web.whatsapp.com has frequently outpaced the Windows app’s development. However, this latest version tends to be slower and consumes more memory.

While it is common for smaller developers to rely on web applications due to limited resources for maintaining cross-platform code, it is disheartening to see a colossal entity like Meta opting against supporting a native app for Windows 11, especially considering the platform boasts 1.4 billion monthly active PCs.

As pointed out by Windows Latest, an update is rolling out for the WhatsApp Beta which replaces the previous native application with a WebView-based platform. The interface closely mirrors that of web.whatsapp.com, but it comes with some noticeable drawbacks, the most significant being its sluggish performance.

Identifying WebView in WhatsApp for Windows 11

WhatsApp Beta WebView — New WebView2 WhatsApp / Image Courtesy: WindowsLatest.com

If you check the Task Manager or a resource monitoring tool like Process Hacker, you’ll see multiple subprocesses associated with WhatsApp. These processes are powered by WebView2, a Microsoft-developed engine that underpins the Edge browser, which is also based on Chromium.

This latest WhatsApp release functions as a desktop container that utilizes web technologies (HTML, JavaScript, and CSS), with WebView2 rendering it in a manner similar to a webpage in Edge. If you’re curious, you can observe the built-in task manager in Microsoft Edge, where you’ll spot helper tools such as GPU Process and Utility.

The same types of helpers are responsible for running WhatsApp on Windows 11, each managing distinct tasks like graphics rendering, network connectivity, and data storage.

WhatsApp Beta native UWP WinUI — Previous native UWP version of WhatsApp

For perspective, the above image depicts the older WhatsApp for Windows 10, built as a pure UWP/WinUI application and operating with a single subprocess. This native app leveraged the system’s UI toolkit, running primarily within a lightweight process.

According to performance evaluations conducted by Windows Latest, the new version of WhatsApp consumes approximately 30% more RAM compared to its native predecessor.

Interestingly, WhatsApp’s support documentation supports this viewpoint, indicating that native applications “offer enhanced performance and reliability”while also providing various advantages, including improved notification management, call handling, screen sharing, and overall user experience.

What Drives Meta’s Move Away from UWP/WinUI to WebView Chromium?

By adopting WebView2, Meta simplifies its development process by maintaining a single codebase for all platforms. However, this transition may also render WhatsApp a resource-intensive application, similar to Chrome.

It is surprising that the previously beloved WhatsApp UWP, which was hailed as one of the best apps for Windows 11, has been supplanted by a web wrapper.

This development comes after praise from Microsoft executives, including Panos Panay, now at Amazon, who lauded the native WinUI app. Unlike many modern Windows applications that incorporate WebView features, WhatsApp for Windows 11 was wholly native.

Readers familiar with previous analyses may recall that the Windows desktop version of WhatsApp consistently maintained feature parity with its Android and iOS siblings, occasionally gaining features ahead of their mobile counterparts.

Unfortunately, this shift signals a regression, as we revert to an experience that is both resource-heavy and uninspired—a disappointing web wrapper.

Source & Images