Re: What is missing for building "real" services?

> WebRTC works great on a webpage, but not in websites. This means that it
> makes perfect sense to use it in SPAs (single page application), but if I
> want to embed it into a website (an ecommerce one for example) - it is far
> from easy - the moment the user leaves the page in favor of another one -
> the call drops.
> This causes a lot of vendors offering click-to-call services that get
> embedded into websites to open up the video/audio session in a separate
> browser window, which then doesn't float around. The experience you get is
> broken due to that.
> Fixing this by having a way for the service to express the fact that it
> wishes to maintain WebRTC sessions across web pages within the same domain -
> or in any other way - will imrpove usability.
This could be fixed when browsers add support to create PeerConnection
objects on SharedWorkers, but unluckily there's no specification
regarding this... :-(

> On a similar note, it would be nice to be able to float the video on top of
> the screen - not the browser window, but the whole desktop (and mobile).
> This enables looking at things in parallel to the conference and still
> having context or the ability to see the people you are talking to.
This can be achieved just by putting the video web page on another window.

"Si quieres viajar alrededor del mundo y ser invitado a hablar en un
monton de sitios diferentes, simplemente escribe un sistema operativo
 Linus Tordvals, creador del sistema operativo Linux

Received on Wednesday, 15 January 2014 22:36:00 UTC