This is a follow-up on WebRTC mandatory video codec debate. Find out how Cisco's OpenH264.org means to WebRTC video battle here.
I did some experiments with WebRTC's getUserMedia() constraints? This lead me down a rat hole but I had some interesting results.
Highlights include:
- Non-obvious Findings
- Mandatory constraints are really suggestions.
- Kill the stream before applying new constraints.
- Use https for a better user experience.
- Don’t bother changing constraints in
I wanted to see if I could WebRTC to help keep an eye on my daughter when she naps. See my experiment here:
https://webrtchacks.com/baby-motion-detector/
Here is the video:
For a technology like WebRTC to be successful, a review on its market is quite crucial. Find out the background and methodology to WebRTC Tool Vendor Directory including the high-level findings like:
- Telecom is making its mark.
- WebRTC in the cloud
- Legacy connectivity features common
- This data is far from
My guide for where to start with WebRTC development tools based on reviewing nearly a hundred different vendors.
Key questions:
- Who are you developing for?
- What kind of development are you good at?
- Are you willing to pay?
- Can you host the solution?
- Do you need to call the PSTN?