Some of you may remember our article from two years ago: “The Worst Part of Building WebRTC Apps”. One thing mentioned in the article (other than testing being painful!!) was that WebRTC mobile support is limited — that was true and what’s also true is that the
TADHack – or Telecom Application Development Hackathon Challenges are taking place in over 30 cities gloabally. You are going and have entered one of the sponsored challenges. You have a prototype idea and WANT TO WIN….but how? Our talented team at webRTC.ventures has won challenge awards the
Most WebRTC implementations require some kind of recording these days, but they are often cumbersome and implementing them is complex. Some even involve docker containers with X-servers running inside capturing a chrome window. Given their implementation complexity, it’s even harder to debug them, so is there an
Why STUN/TURN? In order to do WebRTC across different networks, we need to bypass firewalls and we also have all kinds of restrictions set by ISPs, in order to bypass this restrictions and punch a hole in the receptors firewalls to get media through we need to