WhatsApp will replace its native Windows app with a web-based version

WhatsApp shifts to a web-based Windows app, prioritizing cost over performance.

: Meta is transitioning WhatsApp's native Windows app to a web-based version, deemed inferior due to extra RAM usage and lower performance. The change, reflected in a recent beta update, switches from the Universal Windows Platform to a Chromium-based WebView2 framework, similar to web.whatsapp.com. This move likely stems from financial motivations, as maintaining a single codebase is cheaper. User dissatisfaction is expected as this decision contrasts with Meta's documentation promoting native apps for better performance.

In a move that many users perceive as a downgrade, WhatsApp under Meta's ownership is shifting the focus from its native app for Windows to a more universally accessible web-based version. The transition became apparent with the latest beta update, which saw the app transforming into an empty shell encapsulating the Chromium-based WebView2 framework. The Universal Windows Platform (UWP), previously utilized to enhance performance and user experience, is being abandoned, purportedly due to cost-cutting measures.

The old native application, built to take full advantage of Windows system resources via the WinUI framework, had tangible benefits in performance and reliability. By contrast, the new app functions similarly to the web version, web.whatsapp.com, necessitating increased memory consumption. According to recent reports by Windows Latest, the WebView2 framework causes the app to utilize roughly 30% more RAM, aligning its performance more closely with browser-based experiences.

This shift aligns with Meta's broader strategy, potentially aiming for cost-effectiveness. Meta rakes in $164.5 billion annually; conserving resources by maintaining a singular codebase might outweigh delivering an optimal desktop experience. Critics argue this change mirrors patterns where Meta has historically prioritized its mobile platforms over desktop counterparts, exemplified by their delayed release of a native iPad application 15 years after the device's debut.

Some speculate that this decision reflects Meta's emphasis on its primary demographic of mobile users, overlooking desktop user experience. Official statements from Meta, concerning the revamped application, remain pending, although discrepancies with documentation recommend the old native app for superior performance are notable. Users have expressed concern over the degradation in user experience and performance metrics that stem from this change.

Given the situation, Meta will need to address its audience to mitigate growing dissatisfaction. The company has yet to articulate a comprehensive strategy to refine the web-based app’s stability and overall functionality. Whether this realignment will ultimately serve Meta's or their users’ interests remains to be seen, as similar strategic deviations in the past have reflected increasing mobile dependency at the cost of desktop experiences.

Sources: TechSpot, Windows Latest

SoftwarewebSocial Media