What can browser developers do to differentiate their browser from the rest of the pack when it comes to WebRTC? What will that mean for users?

Cloud and virtualization are said to be different from each other, and I'd like to know how so. Here's your opportunity to help me out a bit.

Gesture interfaces are gaining some nice traction and they definitely show interesting use cases. But will they be used for controlling our televisions anytime soon?

VoIP and UC are all about solving the basics of communication in an IP world. This is about to change by employing the paradigm of the web.

Drum is here to change the way we collaborate in enterprises. Here's an interview with John Logsdon, Drum's Founder & CEO.

WebRTC on mobile is going to be a different ballgame than it is on the desktop. The native web browser is not going to be the delivery method of choice for it.

Martin Geddes recently coined the term Hypervoice. I think it doesn't quite captures what voice will be in coming years - the relation with hypertext just doesn't make sense to me.

WebRTC is going to shift the way we think about communications: from islands being a problem that OTT's brought with their silos into island being the way forward.

Wi-Fi is broken in so many ways it is becoming a bit ridiculous. When it was just a few geeks using it it worked just fine, but now that everyone has it in their pocket, someone needs to step up and just fix it. Here's how the Wi-Fi reception bars are just... irrelevant.

Jive acquired Meetings.io in what can be seen as the second acquisition around WebRTC in under a month. Who will be the next interested companies in acquiring WebRTC startups and what does this say of the market?