1. Generating QR code and a direct URL with an embedded password so that it's easier for sharing and clients to access. Or a page where the user with a provided URL would get the option for QR code too so that they can open it on their phone easily.
2. Responsive site for smartphone and tablet devices
3. Adaptive Bitrate option (already featured...)? And if bandwidth is too low for a remote caller, to drop out a video and leave audio only?
4. IFTTT integration? Easily send a new code to your IFTTT users that you already have on your list, so that you don't need to share it over and over again. They get notification via IFTTT and also automatically opens vmixcall.com for them in their chosen browser. Might work with pushbullet too...
5. Any way to access a call via streaming encoders using protocols like RTMP, RTSP, UDP etc.? This would help a lot for streaming from cameras that don't have browser access or display.


That's all for now :)

EDIT: Made my own HTML QR code and link generator - http://vedranpapes.from....-qr-and-link-generator/, doing something like this on www.vmixcall.com or directly in vMix would be cool! :)

Isn't that what we already do with IP Surveillance cameras and the like. I have cameras and an encoder that I access by merely configuring the RTSP URI.

That's quite a bit different from a remote "Call" which harkens back to telephony or video conferencing.

What they've done with a vMix Call is borrow from the WebRTC realm, where the browser in an end-point. That means that it can be embedded in vMix.

It wouldn't be quite so easy with something like SIP, which is ubiquitous in telephony and VC. In that case the media is sent over UDP typically. It present problems with respect to NAT traversal, invoking things like STUN, TURN and ICE to jump firewalls and routers. Ugh. Complexity.

WebRTC being newer encompasses all of the latest thinking in this area. NAT traversal, encryption, codec options...all settled issues.