Meta Discontinues Native WhatsApp for Windows 11: Now Uses WebView and Consumes 1GB RAM Continuously

WhatsApp for Windows 11: A Step Backward

The latest update for WhatsApp on Windows 11 introduces a significant change that many users will likely find disappointing. This version essentially operates on web.whatsapp.com within a WebView2 container, resulting in a performance decline that reflects a regression to previous limitations.

In a narrative that could provoke cinematic inspiration, we might title a film about WhatsApp’s journey on Windows, “You either die a hero or live long enough to see yourself become a villain.” Once a promising native application, WhatsApp for Windows has cycled back to a web-based configuration, undermining the progress made over the years.

Initially developed as an Electron app, WhatsApp transitioned to a Universal Windows Platform (UWP) format after substantial investment. However, after a span of four years, it has reverted once more to the less efficient WebView2 environment, abandoning its native WinUI architecture.

This shift not only compromises performance but also serves to cut operating costs for Meta, especially after recent staff layoffs that may have disbanded the team responsible for the native application. While Meta reduces expenditures by maintaining the web app framework, users face a frustrating experience.

Performance Issues with the New WhatsApp for Windows 11

Our evaluations reveal that the new WhatsApp application consumes up to 300MB of RAM while sitting idle on the login screen. To put this into perspective, the former native iteration only required about 18MB and could drop to under 10MB when inactive.

Upon logging into the updated version, memory usage skyrocketed to 2GB while attempting to load conversations, with an average usage of 1.2GB when left idle. In contrast, the older native version generally used around 190MB, only occasionally peaking at 300MB during heavy chat activity.

WhatsApp for Windows RAM usage — Comparison of RAM usage between new “WhatsApp” and the older “WhatsApp Beta” (WinUI/UWP)

The potential for memory usage to reach 3GB is alarming, particularly for users managing multiple active chats. Given these figures, the new version falls short in delivering a satisfactory user experience, raising concerns about its availability in the Microsoft Store.

For now, accessing WhatsApp through a conventional web browser such as Edge or Chrome might be a more favorable option than updating to this new WebView2-based application.

A Performance Nightmare?

While high memory usage alone doesn’t necessarily denote a subpar application, the recent WhatsApp iteration feels slow and unresponsive. It also exhibits compatibility issues with Windows notifications and struggles to operate seamlessly with Windows 11 features like Do Not Disturb mode, leading to further notification delays.

Options to Avoid the New WhatsApp Upgrade on Windows 11

According to Windows Latest, WhatsApp version 2.2584.3.0, which replaces the native app, is currently being distributed worldwide via the Microsoft Store. Users are advised to refrain from downloading it, as they might still retain access to the native app for a limited time.

WhatsApp native app — Image Courtesy: WindowsLatest.com

Nonetheless, it appears that users will ultimately be logged out and compelled to switch over to the WebView2 version. This controversial update coincides with the rollout of a more refined WhatsApp experience for the Apple Watch, which has achieved notable popularity, despite Windows hosting over one billion active devices each month. This raises questions about the priorities of Meta and Microsoft in cultivating a valuable experience for desktop users.

Source & Images