If you are a WhatsApp user on Windows, you may have experienced the frustrating reality of using a messaging app that feels anything but efficient. Despite Meta’s vast resources, including a workforce of over 75,000 and cutting-edge AI capabilities, the performance of WhatsApp for Windows leaves much to be desired. The app, which has transitioned to a WebView2 framework, has garnered widespread criticism for its sluggishness and inefficiency, making it a challenge for users who rely on it for daily communication.
With a staggering 3 billion monthly active users globally, WhatsApp’s presence on Windows—a platform boasting 1.6 billion users—should be seamless. However, the reality is starkly different. Users across various hardware configurations, from low-end to high-end systems, report a consistently poor experience. In fact, even before logging in, the app consumes around 400 MB of RAM, raising eyebrows about its efficiency.
Upon logging in, the situation worsens. RAM usage can soar to 1.2 GB while idling, and users experience delays in message delivery that can be anxiety-inducing. The app’s sluggishness is compounded by a choppy scrolling experience, contrasting sharply with the performance of the previous UWP version, which managed to run efficiently even with numerous active chats.
WhatsApp for Windows is a performance nightmare
Users have reported a plethora of issues since the update, including freezing, delayed message delivery, and an overall sense of instability. The app’s tendency to minimize to the system tray rather than closing completely further exacerbates the problem, consuming valuable system resources even when not actively in use.
For those using older hardware, the experience can be even more disheartening. Take, for instance, a typical 10-year-old PC running Windows 11. Despite its age, the system remains responsive with other applications, yet WhatsApp stands out as a significant bottleneck. Users like my father, who prefer typing on a keyboard, find themselves lagging in conversations due to the app’s slow response times, making it a frustrating tool for communication.
What is a web wrapper, and why does it make for a bad messaging app
The crux of the issue lies in the architecture of the app itself. WhatsApp for Windows operates as a web wrapper, essentially loading a web page within a Chromium-based container. This design choice leads to multiple background processes that consume CPU and RAM, creating a cumbersome experience for users. Unlike native applications, which can efficiently utilize the operating system’s notification APIs, web wrappers require constant background processes, resulting in a heavier resource footprint.
Microsoft should not be doing this either
Interestingly, Microsoft is not exempt from criticism in this scenario. Its own Teams application also relies on a WebView2 framework, leading to similar performance issues. While Microsoft has made strides to improve responsiveness, the underlying architecture remains a concern. The company’s approach of restructuring rather than rewriting its applications raises questions about the long-term viability of web-based solutions in a landscape that demands efficiency.
Why Windows keeps getting web apps instead of native ones
The broader issue at play is a trust deficit among developers. Microsoft’s inconsistent history with native frameworks has led many to opt for web applications instead. This trend is evident in Meta’s decision to abandon the UWP version of WhatsApp in favor of a web wrapper, reflecting a lack of confidence in the longevity of native development on Windows.
Microsoft is finally pushing back, but needs to bring Meta along
However, there are signs of change. Microsoft is actively encouraging developers to embrace native app development using WinUI, signaling a commitment to improving the Windows experience. The company is also investing in rewriting its own components in native code, which could pave the way for a more robust ecosystem of applications.
1.5 billion Windows users, and still no native WhatsApp
Despite these developments, the absence of a native WhatsApp for Windows remains glaring. While Meta has successfully developed optimized versions for macOS and other platforms, Windows users continue to grapple with a subpar experience. The disparity raises questions about Meta’s priorities and its commitment to serving the vast Windows user base.
As Meta continues to push users towards the new web-wrapper version, the need for a native solution becomes increasingly urgent. With Microsoft’s renewed focus on WinUI and a commitment to native app development, there has never been a better opportunity for Meta to invest in a native WhatsApp for Windows. By doing so, they would not only enhance user experience but also align with a framework that Microsoft has pledged to support long-term.
My message to Meta
Now is the time for Meta to seize the moment and develop a native WhatsApp for Windows. With Microsoft’s commitment to WinUI and a clear path forward for native applications, the uncertainty that once hindered such investments has dissipated. A native WhatsApp would not only improve performance but also restore trust among users who deserve a messaging app that meets their needs.
