Introducing the WebRTC Developer Tools Landscape

10/07/2017

Time for someone to offer an updated view of the WebRTC Developer Tools Landscape.

Want to learn more about the WebRTC Developer Tools Landscape?

Register to my free Virtual Coffee session

As I am on vacation this week with my family (in Barcelona – ping me if you’re there this week and want to meet and say hi), I will keep this one short.

A few years back, Brad Bush of Genband released a WebRTC Landscape infographic. While he has updated it a couple of times, he since then stopped, leaving the WebRTC space altogether. His site was also lost in the abyss that is the Internet of un-renewed domain names, now hosting a Japanese website promising “services by married women” (Google’s translation).

I figured it was time to create another WebRTC Landscape infographic, but decided to be a bit more focused. Covering the whole WebRTC scene is rather hard, especially trying to do it on the first attempt. Which is why I decided to cover only the WebRTC Developer Tools Landscape in my infographic.

So without further ado, here it is:

I had to modify and update this twice already in the past few weeks – just to keep up with the changes in the industry (adding Safari and removing Tropo).

A few quick notes:

  • Permanent, high resolution, updated version can be found here
  • Need it as a PDF? Get it here
  • Feel free to share this and use it where needed
  • Did I miss you? Ping me and we’ll remedy that – I plan on updating this infographic every couple of months
  • Want to learn more? There’s a free Virtual Coffee session next week that will be focused on this Infographic. Register now

See you next week in my Virtual Coffee 🙂

Responses

Silvia says:
July 11, 2017

Hi Tsahi,
Nice overview! You could add rtc.io to the open source signalling tools.
Cheers,
Silvia.

Reply
    Tsahi Levent-Levi says:
    July 11, 2017

    Will add it in the next round – thanks Silvia

    Reply
      James Fang says:
      July 11, 2017

      Tsahi, as a representative of Agora.io, we also offer a very robust Signaling SDK:
      https://docs.agora.io/en/user_guide/signaling/signal_overview.html

      Similar to the other vendors you list there, it can be used for multiple use cases, including sending client-to-client or client-to-room messages for chat, virtual currency/gifts, etc.

      Reply
        Tsahi Levent-Levi says:
        July 24, 2017

        James,

        I’ve been asked this in many different ways. Mostly on the mobile SDKs, but I guess signaling is no different.

        I’ve placed Agora in the CPaaS domain, because that’s the all-encompassing solution. You offer a service that has it “all” but customers can’t use it unbundled.

        For the same reason, I’d say that Twilio’s IP Messaging isn’t found in the Signaling block.

        I hope this clarifies things a bit.

        Reply
kiss judith says:
July 12, 2017

I am looking for a WebRTC gateway for windows.
Do you have any experience with the Mizu WebRTC-SIP gateway?

Reply
    Tsahi Levent-Levi says:
    July 12, 2017

    I have no first knowledge about it or its popularity.

    I haven’t bumped into it in any of my conversations with vendors out there.

    Reply
Anthony Minessale II says:
July 14, 2017

Just being nitpicky but good job!

FreeSWITCH logo is skewed like its being smooshed.

I think FS fits a lot of those categories and VoIP is the most underwhelming =D
FS has its own native WebRTC stack and does a lot more than just VoIP.

Signalling ? Verto, CHECK!
Media Servers? Conference, video IVR, Video playback, CHECK!
NAT Traversal? ya, CHECK!
CPaaS? Well many of the existing examples use FS, CHECK!
Gateways? Translate WebRTC to SIP, Jingle, TDM etc, CHECK!

Reply
    Tsahi Levent-Levi says:
    July 14, 2017

    Anthony, nitpicking is fine by me (I do it all the time).

    For the logo – email me a hires version. I’ll make sure it is used in the next round.

    For the rest… not so sure.
    Signaling? Yes. There’s Verto, but I’d say if someone only needs a bit of signaling then this will be too complex to wrap your head around.
    You don’t use FS as a TURN server. It would be an overkill.
    It isn’t really CPaaS. You can build CPaaS with it, but that’s almost always true for all the rest of the categories.
    Media server? The same. No one contemplates between Kurento, Jitsi and FS. Even if FS has similar/same capabilities (and I don’t know if they are similar/same).
    Gateways? Yes. You can use FS. And it is used for it. But it isn’t a Gateway.

    I don’t know of many who use FS when SIP isn’t needed, so for me, it sits nicely in the VoIP category.

    Might be a mistake on my part, but it is how I see things.

    Now that said – I do plan on enhancing the whole landscape thingy in the near future with a document that goes along with it. Will add more textual information and explanation in that one so things are clearer.

    Reply
Sam Kaufman says:
July 21, 2017

@Tsahi I’d add https://github.com/meetecho/janus-gateway to Gateways/media servers. I used it for an early prototype of BugReplay before MediaRecorder was added to Chrome.

Reply
Paul M says:
July 21, 2017

Your virtual event link doesn’t seem to work.

I want to register…!

Reply
    Tsahi Levent-Levi says:
    July 21, 2017

    Paul,

    These virtual coffee sessions are only open live to non-customers. I am working on a way to get access to them in such cases, so check out my site some time next week.

    Reply
Lennart Grahl says:
August 2, 2017

Hey Tsahi,

would you like to add the SaltyRTC signalling protocol in the next round? https://saltyrtc.org

I’m also wondering where standalone implementations such as RAWRTC (data channel only so far – https://github.com/rawrtc) would fit in.

Cheers,
Lennart

Reply
    Tsahi Levent-Levi says:
    August 3, 2017

    Lennart,

    I think both are too small to fit into what i have in mind for the landscape. Once they get more publicity and adoption it will make a lot more sense.

    In the meantime, may I suggest you add it to the WebRTC Index?

    Reply
      Lennart Grahl says:
      August 9, 2017

      I would have thought at least SaltyRTC should be interesting as it is currently unique (to my knowledge) in its approach towards end-to-end encryption on the signalling level where the server does not need to be trusted and is completely substitutable with another one.

      The problem I have with the WebRTC index is that it focuses on companies which neither of these projects is associated to.

      Reply
        Tsahi Levent-Levi says:
        August 9, 2017

        There are now 7174 repositories on github mentioning WebRTC. Being unique or interesting is hard to measure…

        And I do believe that Matrix is supporting end-to-end encryption on the signalling level.

        Reply
Lennart Grahl says:
August 9, 2017

Yep, knew about Matrix but it’s hardly comparable to SaltyRTC as Matrix is pub-sub based, has registration, login, server-based rooms with permissions and membership, etc. Basically, it provides a lot of features that bind users to a server and signalling is just a small part of it.

SaltyRTC on the other hand focuses just on the end-to-end encryption of the signalling (WebRTC, ORTC or whatever you want) and arbitrary data transfer. The server only exists as a rendezvous point and for relaying data which makes it substitutable.

A note on popularity: While the protocol itself may not be obviously popular, [Threema uses it for their web client](https://threema.ch/en/threema-web) and they have a substantial market share regarding IMs, at least in German-speaking countries that is.

Reply

Comment