Forget Whatsapp - Facebook Messages goes WebRTC - Big Time

Silly me put my fortune on Whatsapp going WebRTC, but Facebook decided its Messenger should be getting it.
Just last week I've written my impressions on Whatsapp getting voice, and Facebook unbundled its Messenger from Facebook. In the web browser.
Just head to messenger.com to get an experience similar to Whatsapp's web app. The main difference is that login is done through Facebook and not a QR code linked to your smartphone.
So I tried it out. And yes. It uses WebRTC. Natively. Right in my Chrome page:

Why I find this move VERY interesting
- Facebook had an agreement with Microsoft/Skype for voice and video calling
- That agreement is long gone. I've been an early advocate of Facebook going it alone with WebRTC and ditching Skype
- Facebook could have gone with some other OTT player, but it has decided to take things into their own hands. Communications for them is a feature and not a service - as it should be
- Internet Explorer and Safari haven't confused Facebook. They didn't wait for Microsoft's implementation. Messenger works on these browsers, but just won't show the WebRTC calling options
- The same (or almost the same) is available from within the main Facebook site for some time now. It is still there - WebRTC video calling included. Unbundling messenger from Facebook in the web app is an interesting move. Not sure why they did that


Well, the web part has been around for a while, since mid-january at least. It was quite similar to apprtc terms of architecture.
And the messenger.com app third party license notice shows both libjingle and webrtc.
Fippo, thanks.
I noticed that Facebook had it for awhile. The fact that they made it an integral part of their standalone webapp is the interesting part here - they definitely see value in it.
heh yeah. I was hoping for this to interoperate actually. Just found my notes... do they still run their TURN server on the odd port 50021?
{ servers: [stun:stun.fbsbx.com:3478, turn:173.252.79.85:50023?transport=udp, turn:173.252.79.85:3478?transport=tcp, turn:173.252.79.85:443?transport=tcp], iceTransportType: all }
If I understood correctly, their desire to build almost from the ground up is more to do with their ambition to measure and quantify everything.
Maybe Varun. I guess that developing on their own was made possible (and relatively cheap) by WebRTC that it made partnering and diluting their brand name not worth it.
Are you saving the Business tab on the messenger page for another blog post? That's the biggest story there!