Hacker News new | ask | show | jobs
by wbobeirne 1485 days ago
Our team got off the ground really quickly using https://github.com/feross/simple-peer to handle the majority of the WebRTC client implementation. We're sending video and voice, so websockets aren't feasible. I'd say it was a lot easier than I expected coming in cold, and about 95% of connections establish quickly and don't have any problems.

However for that remaining 5%, I have a lot to learn. Using an abstraction is great when it works, but I'm interested in going through OP's project to get a better sense of what's happening when things go wrong.

2 comments

You're so right. In most cases, you won't have a problem if you implemented it with existing products, but for 5%, lots of cases may happen :) The complete reason behind WebRTC Nuts and Bolts is this!
Glad that simple-peer was helpful to you :)