Meta's recent decision to replace WhatsApp's native Windows application with a Chromium-based web wrapper has sparked considerable discussion among users and industry experts. This shift marks a significant departure from the company's previous commitment to platform-specific optimization and raises questions about the future direction of desktop applications.
The original WhatsApp desktop application for Windows was celebrated for its native implementation using the Universal Windows Platform (UWP) and Windows UI Library (WinUI). This design allowed the app to operate as a lightweight, single-process application that seamlessly integrated with the Windows operating system. Microsoft executives, including former Windows chief Panos Panay, lauded it as an exemplary modern Windows application.
In contrast, the new version utilizes Microsoft's WebView2 technology to package the web-based version of WhatsApp into a desktop container. This approach introduces multiple subprocesses that handle graphics, networking, and storage operations, resulting in approximately 30% higher RAM consumption compared to the native app. Users have reported observing several WebView2 helper processes in Task Manager, indicating the increased resource usage.
Meta's support documentation has previously highlighted the advantages of native applications, stating that they "provide increased performance and reliability" along with superior notification experiences, calling capabilities, and screen sharing functionality. The transition to a web-based wrapper appears to contradict these assertions, as the new app offers a more basic settings interface and altered notification behavior that feels less integrated with Windows 11's design language.
On the positive side, the beta version of the web wrapper app introduces features such as WhatsApp Channels and enhanced Status and Communities functionalities, which were previously available only through the web interface. These additions aim to provide a more unified experience across platforms. However, they come at the cost of the streamlined, integrated experience that the native Windows app offered.
The shift to a web-based wrapper allows Meta to maintain a single codebase across all platforms, potentially simplifying development and maintenance. This strategy aligns with the broader industry trend of using web technologies to create cross-platform applications. However, it raises concerns about performance and resource efficiency, especially for users who valued the native app's responsiveness and integration.
As of now, Meta has not announced when the web-based version will replace the current native app for all users. The company may be using the beta phase to gather user feedback and address performance issues before a full rollout. Users who prefer the native experience may want to provide feedback to Meta to influence the development direction.
In conclusion, while the introduction of new features in the web wrapper app is a welcome development, the transition from a native to a web-based application raises important questions about performance, resource usage, and user experience. It remains to be seen how Meta will balance the benefits of a unified codebase with the need to provide a high-quality, responsive desktop application for Windows users.
Source: Times of India WhatsApp is dropping its native Windows app that Microsoft exec called “exemplary modern Windows app” - The Times of India
