Keep on top of the changing landscape of WebRTC development and behavior
There are two ways to use WebRTC if you’re investing in it for the long run:
Actively working towards knowing everything there is to know about the WebRTC ecosystem.
Check out discuss-webrtc, browser bug trackers and other forums across the internet each and every morning. Look at code changes submitted to libwebrtc and figure out if it relates to you.
That’s the way to do it! But are you sure you’re not missing something? And is it worthwhile to invest so much time and effort?
We’ve seen it time and again. Developers are getting surprised by a new breaking behavior of the latest Chrome release - one they could find out about and resolve a month earlier. Companies failing to update their native libwebrtc implementation and then being exposed to a known vulnerability.
Keeping track and staying on top of it all is quite a commitment. One that only specific developers have the inclination to do. Which is why we decided to step up and help you out.
Here is what we're enabling here:
This way, we’re going to separate the wheat from the chaff for you with all that information out there.
What’s WebRTC Insights?
WebRTC Insights is a unique service by Philipp Hancke and Tsahi Levent-Levi that keeps track of the things that matter to you for you.
Instead of having your developers sift through Chrome bug reports and updates, W3C emails and other news items, we bring it to you directly.
- Get you actionable insights on things happening in the WebRTC ecosystem that affect your development
- Reduce time and frustration you spend on WebRTC issues and let you focus on core business
Every 2 weeks, you and your team will be receiving an email with the latest WebRTC Insights issue. The issue is delivered as a PDF covering everything relevant to you that happened in the past 2 weeks.
You will be able to use this concise and actionable issue to tweak your plans and make both short term and long term changes in your WebRTC development based on it.
What our clients say
About WebRTC Insights
The WebRTC Insights has quickly become critical to our planning. It makes it easier for us to keep up to date and make informed decisions in our roadmap and engineering related to WebRTC. Everyone developing with WebRTC should read it.
Øyvind Reed // CEO @ Whereby
For any Service Provider or Apps who heavily relies on WebRTC, the WebRTC Insights offers great value. Developers now have a well-organized reference to quickly understand known issues and industry trends to stay ahead of the curve – it really bridges the gap for developers who are not closely involved in WebRTC stack development but yet relies on it.
What I like most about the Insights is its bi-weekly cadence, which fits the rapid Chrome/WebRTC release cycle, and most of the mentions are actionable for us. With the recent Safari audio breakage, the Insights highlighted the problem timely and saved us a lot of troubleshooting effort.
Jim Fan // Engineering Director at Dolby Laboratories
In praise of Philipp & Tsahi
If we consider WebRTC in its entirety: an implementation, a library, a browser API, a set of protocols, a community of developers and an ecosystem of apps and services, then there are arguably less than 5 people on the planet who can be considered gatekeepers of all knowledge WebRTC. Philipp is undoubtedly one of those five. Any journey on the WebRTC path that is backed by him is tremendously more likely to succeed.
Emil Ivov // Head of Product, Video Collaboration @ 8x8. Jitsi Founder & Project Lead
Tsahi is a rare occurrence in our industry as he combines a laser sharp understanding of various technologies with a grasp of business strategy and market trends. There is simply no match to working with Tsahi when it’s about transcending the marketing noise, sales pitches and wishful thinking.
Itay Rosenfeld // CEO & Voxbone
Inside the WebRTC Insights
Each issue of the WebRTC Insights includes the following sections:
- From the issue tracker - a prioritized list of bugs that were issued or updated across the major browsers, related to WebRTC
- Mailing lists & PSAs - a prioritized list of issues and discussions we found relevant to bring to your attention
- Chrome origin trials - a best effort list of the ongoing origin trials that Google is conducting in Chrome which are relevant to WebRTC
- WebRTC Security - an ongoing log of our own about security CVEs (known vulnerabilities) in WebRTC. Since Google doesn’t maintains a good list, we decided to create one just for you
- Market Insights - a review of the market trends and major developments and announcements we think you need to know about
The monthly brainstorm
An optional piece complementing the WebRTC Insights is the Monthly Brainstorm:
This is an online session, where Tsahi Levent-Levi will sit together to understand better your challenges, share his own knowledge and experience and assist where he can.
This meeting will have an agenda set to it in advance and prepare for it as necessary.
In these sessions, Tsahi will offer his own suggestions, and if it makes sense, will gather more information through his network of contacts to assist you further.
Focused and to the point
Customized and personalized
For enquiries, samples and subscription, fill out the form below:
We are here to help, which is why we decided to send this via email. You can always hit the reply button on the insights email you receive and answer us questions related to what’s in there.
Yes. Definitely. Open source is great - we’re all for it. But you kinda get what you paid for.
There’s a lot of maintenance and optimization work you need to do with open source media servers, and the WebRTC Insights can help you out in prioritizing that work.
Probably not. Unless you are planning on switching to developing your own infrastructure, in which case, it might be wise to subscribe for a month or two to understand what’s ahead of you.
Monthly and yearly plans are available.
Payment can be made via wire transfer, PayPal and credit card.
That’s a matter of perspective.
If you have a developer investing his time in it, then he is probably pouring 20 hours or more a month on it. If you don’t, you should consider the price you’re paying by being left uninformed.
I'd also consider the price of missing a security patch, a PSA or a bug that you could have found a month or more in advance with the WebRTC Insights.