I admit that I am reversing myself on this idea. Where once I thought that just using the browser on an Android device would be sufficient, I now realize that this is too complicated for many mortals.

Earlier this month I was at Cluecon in Chicago, which is a telecom developers conference. The people gathered there included some of the leading minds in the WebRTC world.

In particular, Emil Ivov of Atlassian gave a great presentation on WebRTC. He's the lead author of Jitsi Video Bridge, the first open source SFU. It;s a truly impressive piece of work. He's also a friend who I've interviewed several times for our show http://vuc.me

One of his major points was "don't forget about mobile." It's a point that stems from their release of the mobile client for JVB, which is also open source. The mobile experience can work in a browser, but be a easier in a dedicated client.

I understand that vMix Call is based upon Appr.tc. That implies that there's some potential to leverage some of the work in the JVB mobile client and offer a vMix Call mobile client. At very least, there's a model to be explored.

By the way, Atlassian and also an Australian company.

+1

Add the ability to work over WiFi on local network and that would be golden!

+1

Btw, whats current behaviour of vmix call in local network? Does it use full internet bandwidh to send video stream between to 2PCs that are on the same network or does it only use internet to "find each other" and after that - it sends video locally?

+1

+1!

Please consider this if you make an Vmix Call mobil app:

Instead of only using the Call future as a conference call, make it possible to use it as a mobile camera.
Built in onscreen tally light. The chat function will display messages onscreen for communication. Or maybe the sound sent to the mobile could be used as a way to communicate to the "camera-man"

I'm using a custom setup to make a 16 hour streaming of IronMan races i Denmark, with 4-5 mobile as cameras. But this would be a game changer for me! Thanks!