WhatsApp has recently rolled out a new version of its Windows application, and ironically, it seems to perform worse than its predecessor. The newly released version 2.2584.3.0 has replaced the previous native UWP app with a web wrapper utilizing Microsoft’s WebView2 rendering engine, leading to considerable performance concerns.
On October 31, Windows Latest noted that WhatsApp was preparing to shift to a Chromium-based web app starting November 5. However, Meta provided little information regarding this transition from UWP to the Chromium-based Web Wrapper, aside from an alert that users would need to log in again after the update.
This transition has been in progress for several months, with reports dating back to late July indicating that the WhatsApp Beta version had already migrated to web.whatsapp.com.
Come November 5, Meta initiated the anticipated update for all WhatsApp users on Windows. Early users reported that the updated app functions similarly to the beta version, merely loading web.whatsapp.com in a WebView2 container.
Performance Review of the New WhatsApp for Windows
During testing of the WhatsApp Beta version, it became clear that despite expectations for increased stability and performance, issues remained. Users have reported that even before logging in, the Beta version consumes three times more RAM than the traditional UWP version, indicating a concerning trend in resource usage.
Before logging in, the new app showed a startling RAM usage of 300MB. In contrast, the UWP version, which was already logged in and active, only utilized just under 100MB of RAM. This disparity raises serious questions about the efficiency and optimization of the new app.
The login experience, although familiar, was accompanied by a pop-up alerting users of changes, including the introduction of Channels and enhanced functionality for Status and Communities—features that many users of the UWP app did not appreciate and wish to disable.
Despite some aesthetic modifications, long-standing issues regarding performance and responsiveness remain evident. Many users report a frustrating lag when transitioning between chats, which can take seconds to load despite previous swift performance in the UWP version.
Impact on User Experience
The new interface is notably less user-friendly, particularly when it comes to resizing the chat window. The new Chromium-based WhatsApp struggles to allow users to adjust the window size to focus solely on current conversations, affecting the multitasking experience.
RAM Utilization and Hardware Implications
The new WhatsApp design results in excessive RAM consumption, which is particularly problematic for users with limited hardware resources. My laptop operates at a concerning 90-95% RAM utilization, struggling under the weight of the new app’s requirements, which can peak at over 600MB when idle.
This heavy RAM usage for such a basic application, particularly in the context of resource constraints, suggests a need for users to either adapt by closing other applications or consider hardware upgrades.
The extensive resource demands don’t stop there; even when closed, the app continues to run processes that consume RAM and CPU, leading to sluggish performance. Users can mitigate some of these issues by adjusting settings to prevent the app from running in the background, but this isn’t a fail-safe approach.
Concerns for Older Hardware
For users with older hardware setups, these adjustments necessitate a profound reconsideration of their current machines. For instance, on a less capable PC equipped with 8GB of RAM, the new WhatsApp version easily drains available resources, forcing users to contemplate hardware upgrades for basic functionality.
Video Call Challenges
Video calls on the Chromium-based application significantly exacerbate resource consumption issues, utilizing upwards of 900MB RAM while demanding more processing power than the previous UWP version, which remained efficient with a usage of only around 316MB during the same activities.
Technical Issues and Limitations
Additional concerns have been raised regarding functionality in the new app, including glitches in viewing status updates, repeated loading screens, and unresponsive behavior after switching chats or opening images. Such issues were virtually non-existent in the simpler UWP version.
Understanding the Shift to Chromium-based Model
The performance decline is rooted in the architectural differences between the native UWP app and the new Chromium WebView2 model. The latter operates more like a mini-browser, and the associated resource requirements reflect this change.
While this shift ostensibly aimed to unify development efforts and streamline updates across platforms, it has resulted in compromised performance and increased demands on system resources. Questions remain about the long-term viability of maintaining such an architecture.
The Strategic Decisions Behind Meta’s Changes
Meta’s transition from a native app to a web-based structure seems to stem from financial decisions and the need to optimize resource allocation amid broader economic challenges. With the focus shifting towards AI and other emerging technologies, traditional app support appears to be waning.
Notably, the retention of a functional macOS app juxtaposed against the abandonment of a native Windows client raises eyebrows, suggesting a discrepancy in how Meta prioritizes cross-platform development.
In conclusion, the transition to a Chromium-based WhatsApp for Windows presents numerous challenges that affect usability and performance. While the changes are marketed as improvements, the reality indicates that many users, particularly those on older hardware, could face significant drawbacks. As discussions about software functionality and resource management continue, it remains critical for developers to prioritize user experience in future iterations.
Related Articles:
Microsoft Recommends 32GB RAM as the Ideal Upgrade for Windows 11 Gaming
19:34
Satya Nadella Confirms 1.6 Billion Monthly Windows Users and Bing Surpasses 1 Billion Users
15:14
Satya Nadella Acknowledges Microsoft’s Need to Regain Windows 11 Users and Enhance Performance for Low RAM Computers
0:54
Leave a Reply