WhatsApp to launch voice calling in the second quarter
theguardian.com
theguardian.com
The client is light and fast. I can use it a dozen times a day and it doesn't get in the way. Skype, et al by contrast are bloated because every new release must add new features. By the time version 20.0 comes out, it's bloated.
Same thing keeps happening over and over again with torrent clients. It happened with WinAmp and to MS Word and nearly every other software that gets popular.
You can almost see the thinking machinery in work. "450 million users? How much are we making per user? $1 per user per year, that's it? Let's get into VoIP, it's a billion trillion dollar per annum industry. Let's get the project managers to layout the roadmap for the next year and set the milestones so we can get there fast."
Both use the same underlying technology (XMPP) and both know how to use the protocol, but it's still very hard to pull off at this scale once you allow multiple devices to login with the same account.
Skype just has vastly more features, that's why they have these synchronisation issues.
Since when does Skype use XMPP? AFAIK, it uses a closed protocol. It appears that Whatsapp does indeed use XMPP under the hood, though.
As for Skype, it's absolutely terrible at handling multiple devices. It would get much better if the app phoned home when a given message arrived on a Skype client with a focused window, in order to prevent/cancel already existing alerts on other devices.
With MS' Lync at work, if I forget to signout on my phone, a few times a day, my phone grabs an inbound message that never shows up on my desktop, and I totally miss the conversation. Skype has a lot of similar issues, and it's painful at best.
What I REALLY want is something for the workplace to kill Lync...
Just one example....when the connection is bad, it degrades audio and video, so neither is usable. And we won't even start on the nightmare that's the UI.
That MS paid a king's ransom for this and has done nothing with it since boggles the mind.
Microsoft also has a product called 'Lync' that (from what I've heard) is not doing so well, so I believe their goal there again is to roll their users into Skype and eventually discontinue that product. Buying Skype was all about trying to salvage their brand from the shortcomings of their own software.
It's doing pretty well in its market (Enterprise) because despite the demands (federation requires two servers) it's better than the competition (WebEx).
The client is slightly less annoying than Skype if only for the fact that it doesn't take over your entire computer for IM like the new Skype client does.
1) the mac client is buggy/crashy and sucks.
2) the mac client doesn't properly register itself so meeting links in outlook work.
3) when you are signed in on multiple systems, phone, home, work, messages aren't synchronized like gtalk/hangouts so you will miss a lot of conversations if you forget to sign out, this happens with my phone a couple times a week.
4) on a retina mac, the screen sharing only works on 1/4 the screen.
5) the UI in the android app is about the worst I've used for a productivity app on android.
On windows it's a bit better, but the non-synchronized conversations really irks me to no end.
Exactly! What do you have Skype installed on your smartphone?
A year from now on you might be saying: "Hey John Doe, I WhatsApped with my SO yesterday and asked her/him can I buy him/her some nice undies. You know what, today Facebook business pages are posting underwear ads on my wall!"
... or because skype clients start to "sync" with old chats when a different device comes online.
Immediately the call was clear as day. It dropped once or twice, but the quality was pretty high otherwise. If I can find a WebRTC client with a few more features, I may never use Skype (or any other XMPP video chat) again.
I've played with it a little on my phone even, and though it barely works, you can see the potential. All I can say from it all, it would be nice if MS/IE could play better with others.
This may also be a regulatory request from the U.S. Govt. If you call in a bomb threat from Voice, the gov't can track you down.
When you make calls from within gmail, your endpoint is a google server but google is still making a regular telephone call and just bridging the two.
I'd actually consider WhatsApp behind its Asian competitors in terms of features. They also might be an indicator of what features we might see roll out with WhatsApp.
Eh, not really. You get the notification (no guaranteed delivery time), open it up, it opens up the app, which takes a few seconds to load... before you know it the other person is going to have hung up.
iOS' current backgrounding APIs strike a fairly acceptable balance between functional background tasks and battery life. Let's say if Apple took the reigns off background in iOS, we'd see some app developers ravage the battery and see users having terrible device experience.