WebRTC has no specific programming language to it. The components that comprise a WebRTC service utilize different languages. Here’s how it all fits in (and what you should know).
An overview on the different alternatives available when you recording WebRTC sessions: server side, client side and forwarding.
When we look at network connections of WebRTC, most of the time you’ll see people focusing on signaling but missing the WebRTC media paths. Here’s what to expect.
Using a media server with a public IP address isn’t enough to solve your WebRTC NAT traversal headaches – you need a TURN server for that.
Kurento or Jitsi? This is a question I hear quite often from people who want to build their own service. Here’s how I look at it, and what drives my own decision making processes.
You should drop the idea of using a WebRTC plugin and warm up to the use of an Electron WebRTC app instead – you’d be surprised who’s using it already.
VP9 is starting to find its way into chipsets, making VP9 hardware acceleration a reality. How is this turning out, and what the future of video coding looks like?
H.264 is about to become the popular choice for WebRTC developers. Here are a few reasons why this is happening.
WebRTC forces enterprises and developers to embrace agile. Not only in their R&D, but throughout the whole product lifecycle.