3 ms·
XMPP performance on mobile platforms, especially on subpar networks, is pretty bad. It's designed for always-on networks and is a huge battery drain even if yo
by nasalgoat 14y ago
XMPP performance on mobile platforms, especially on subpar networks, is pretty bad. It's designed for always-on networks and is a huge battery drain even if you can maintain that connection.
- shmerl 14y agoWhatsapp uses XMPP nevertheless. That's not the problem. The problem is that it modifies it, to make it non compliant, it doesn't federate and it also offers no way to control your user name and password, using phone hardware identity instead. There are several ways to address XMPP energy drain, some of which were proposed as XEPs. Google uses one of such methods (google queue). Facebook uses another. Example: https://bugs.freedesktop.org/show_bug.cgi?id=38943 https://bugs.freedesktop.org/show_bug.cgi?id=38943
- somesay 14y agoXMPP is used for Facebook Messager, Google Talk and even WhatsApp. Just WhatsApp adds proprietary options to it and does some weird key exchange on first signup. So there is e.g. no chance to log in from your computer or simultaneously running it on multiple devices. You are right, a permanent connection isn't that great on mobile phones, but as a custom XMPP service you could just use push technology like every other app, too. That's what e.g. Google and Facebook are doing. Beejive and IM+, two common mobile IM apps with XMPP support, are doing this, too. The only downside is, that since they don't want to store you credentials, you have to run the app to reconnect to your XMPP server and delegate that connection to their push servers. This is just a bit annoying when either jabber.org or their servers have connection errors.