Re:Meta replaces WhatsApp for Windows with web wrapper that ...
by savolai on Thursday November 13, 2025 @05:59AM
(#45913415)
If you can deploy your wxwidgets app as a networked app in the browser too, then sure.
[ Parent
| on HN ]
Re:Meta replaces WhatsApp for Windows with web wrapper that ...
by 72deluxe on Thursday November 13, 2025 @06:17AM
(#45913555)
That's not what the issue here is.
The issue is not that a native Windows app needs to run in a browser.
The issue is that a native Windows app has been replaced by yet another browser.
Re:Meta replaces WhatsApp for Windows with web wrapper that ...
by savolai on Thursday November 13, 2025 @08:47AM
(#45914856)
Yes. Arguably because of the organisational cost of maintaining both a web version (which they arguably need) and a native windows version (which they arguably don’t need).
Re:Meta replaces WhatsApp for Windows with web wrapper that ...
by skydhash on Thursday November 13, 2025 @09:47AM
(#45915501)
Most of WhatsApp is UI veneer on a set of webservices. Unless they’ve architected their app badly, I’m not seeing the cost of maintaining a native software being substantial.
Re:Meta replaces WhatsApp for Windows with web wrapper that ...
by lbreakjai on Thursday November 13, 2025 @11:09AM
(#45916607)
If the cost is > 0 then businesses see it as money wasted if a solution where cost = 0 exists.
Re:Meta replaces WhatsApp for Windows with web wrapper that ...
by sheepscreek on Thursday November 13, 2025 @10:44AM
(#45916247)
Ironically, you can actually do this with wasm.