Good news for those of you like Viber (see site), the mobile VOIP solution that millions are using on the iPhone and Android these days, as the app is set to come to Windows Phone in early 2012.
Viber has an interesting history with Windows Phone. They lamented the "closed" system very early on, noting that they would not bring their app over simply because they could not due to the lack of codec support. In turn, they were quite public with their dissatisfaction with the Windows Phone development process.
Fast forward and guess who got involved? Yup, Brandon Watson. Back in July, Watson stepped into the Twitter conversation with Talmon Marco, founder of Viber. Watson simply asked "...Have you had a conversation with anyone on #wp7dev phone team yet? Can we start one?" which from what we understand, go the ball rolling.
Since the, the Viber team has worked with Microsoft and got the native access they needed for their codecs. In turn, with the increased market share for Windows Phone, means we should see a Viber client in the next few months, according to their Facebook page. Sounds like another win for Windows Phone and with Kik Messenger and WhatsApp, should bring some new folks over. It also demonstrates how Microsoft is flexible and willing to work with devs, who ask.
Daniel Rubino is the Executive Editor of Windows Central, head reviewer, podcast co-host, and analyst. He has been covering Microsoft here since 2007, back when this site was called WMExperts (and later Windows Phone Central). His interests include Windows, Microsoft Surface, laptops, next-gen computing, and arguing with people on the internet.
Hi everyone, just wanted to be the only person to comment on this post. Personally, I have never heard of Viber.
you just did :D
VOIP on WP is a great idea looking forward to this app coming to the marketplace
This is great news looking forward to use the app
Get the best of Windows Central in in your inbox, every day!
Thank you for signing up to Windows Central. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.