This website could be a lot more useful if it answered these questions:
* How good is this compared to other alternatives? (Or why choose this instead of something else?)
* Where are the client apps for this, more importantly on mobile?
* How good is this compared to other alternatives? (Or why choose this instead of something else?)
* Where are the client apps for this, more importantly on mobile?
And it is very actively developed, which is arguably the most important metric in the current webRTC environment. Since the spec and browser implementations are a fast moving target right now and for the years to come.
Comparing Jitsi with mediasoup is like comparing Netflix (backend + apps) with Express.js + libcurl.
Jitsi developers may replace their RTC core internals (including the SFU) with mediasoup + mediasoup-client and you wouldn't even realize of it. Hope this helps.
And here's the source code for the demo: https://github.com/versatica/mediasoup-demo/
Libs for native apps: https://github.com/haiyangwu/mediasoup-client-android
In general, i recommend it. Only media server that i saw working (slightly) better is Jitsi, but it is 10x more cumbersome and time-consuming to learn.
Those libs for native apps are not official mediasoup components. We deliver libmediasoupclient[1] which is a native C++ implementation of the JS mediadiasoup-client[2] and uses libwebrtc[3] C++ native code directly.
Those two libs for native apps make use of libmediasoupclient, but they are not written nor maintained by us. Having said that, to the moment there is no official Android or IOS native client but there is libmediasoupclient which will be the core for both.
[1]: https://github.com/versatica/libmediasoupclient [2]: https://github.com/versatica/mediasoup-client [3]: http://webrtc.github.io/webrtc-org/native-code/