WhatsApp finally has a quick and light application in Windows. Joy will last little

Meta launched WhatsApp for Windows and Macos In 2016. Since then, until 2022, the company had A slow and very little efficient customerfor a single reason: it was not a native application, but a web container based on WhatsApp Web, which implied slowness and enormous consumption of RAM.

Better changes, changes worse. In 2022, WhatsApp on desktop made an praise leap forward, launching native messaging customers on both platforms and discarding the previous technology. According to Our own teststhe use of RAM in Windows went from 500 MB to 100 MB. The use of CPU making scroll, from 60 % to 20 %. Three years later, one step back, according to Windows Latest: WhatsApp beta (downloadable here) It is no longer native, it is a web container again that camouflages a browser.

Bad news. According to Windows Latest observations, made by analyzing the WhatsApp Beta processes in Windows Task Manager, Meta is using WebView2a technology that allows using the Microsoft engine within applications. Your own version of Framework Electrona standard in the industry. The bad news for the user in front of the application has nothing to do with using WebView2 in particular, but with abandoning the previous approach.

This inefficient will be the new WhatsApp in Windows.Every time we open the new version, the application will have to load the web version internally, and in the background, an instance of the Microsoft Edge browser, on which Webview2 operates. Just as it happened with the version they developed from 2016 to 2022. It is very inefficient with respect to an application that uses Native Windows development platforms, such as UWP (Winui).

In the absence of being able to prove it, Windows Delast tests demonstrate the step back, and are related to those made in Xataka in 2022. The new version of WhatsApp Web consumes 30% more of RAM than the version available until today in the Windows application store. It is a developing version that can be optimized more, but leaving the native approach has inevitable negative consequences. In Reddit Han accomplished that the new client consumes up to 1 GB of RAM.

Goal explains why a native application is more efficient. When they launched the current client, goal created a website in which they explain the Benefits of a native application very clearly:

• “They provide greater performance and reliability, more ways of collaborating and functions that improve your productivity”
• “They are designed and optimized for your computer operating system”
• “They offer greater reliability and speed”

Why use web apps instead of native. Being so clear the advantages of a native development, and even being defended by goal, why go back? The industry resorts to web -based applications for a very simple reason: unify developments and guarantee functions and compatibility parity between different operating systems.

If a company builds a single website, you can easily adapt it to Windows, Macos, Windows, Linux and Android, as well as offer it in browsers. Optimization is sacrificed, but the deadlines are expedited and the size of the equipment required to move forward and maintain a project is reduced. Mark Zuckerberg himself said that IOS’s old Facebook app was bad because it was based on html. They went to native development and everything improved. The same In Android.

Image | Antonio Sabán with Ia

In Xataka | Every time someone tells me that his mobile is slow, I know where to look: the “paper” of WhatsApp