WebRTC Weekly Issue #29 - August 20, 2014

It’s August and hope you’re enjoying your summer! Here is the latest on WebRTC  from your friends at webrtcweekly.com


Dear CEO (of a node-powered corporation) (hueniverse.com)
This can be related to WebRTC in two ways: Replace the word Node in the article with WebRTC and then read it. Or if you are using Node.js – read this as well…

Why RCS Failed (blog.audiocodes.com)
Hint: over-standardization

Gruveo Security Explained (gruveo.com)
The details in this one? They are correct for 99% of WebRTC services that wish to be commercial. Compare that to your VoIP provider (who has some of it and only in “optional” form).

WebRTC and Designing Realtime Experiences (thewebplatform.libsyn.com)
If you are into podcasts, then this one about WebRTC may well be for you.

Metrics for Over The Top Telcos: From Nodes to Flows (letmydatago.org)
Phil Wolff’s take on engagement metrics for communications services.


WebRTC for Enterprise: Challenges and Solutions (tokbox.com)
Don’t let the title fool you. This one covers challenges/gaps/topics related to WebRTC for anyone. A good read.

Progress with rtc.io (gingertech.net)
rtc.io, a WebRTC signaling framework, can now be used with backends other than Node.js.

Use Cases and Customer Wins

Creating an Email Click To Call Service with WebRTC and Voxbone (voxbone.com)
Technical, but also a use case. Voxbone provides step by step instructions on adding click to call button to emails using their service.


Summer time I guess… but at least we have an EOL announcement:

Announcing the end-of-life of the OpenTok 1.0 platform (tokbox.com)
TokBox is killing its old Flash platform and from now on it is WebRTC only.

From our own posts