- From: Svein Yngvar Willassen <svein@comoyo.com>
- Date: Thu, 2 Jan 2014 20:57:09 +0100
- To: public-webrtc@w3.org
I'd second most of what has been said in this thread so far. You can build a real service with WebRTC. Our service appear.in shows that. It is also true that many of the issues we've previously had to work around have disappeared with newer browser versions. That being said, some issues remain. The following are common issues / requests we get from our users that we feel must be addressed by the browser. (Either by spec or just browser implementations): - Missing echo cancellation and other audio issues, particularly when there are more than two participants in a conversation. (Audio should be more stable / higher prioritized than video, currently it often seems opposite.) - NAT traversal and connection stability issues. - Screen sharing with better quality which also works in other browsers than Chrome. - Ability to renegotiate streams, for example lowering image resolution without stopping and starting the stream. - Ability to record streams. - Support in iOS and the Safari and IE browser. (Probably little the WebRTC community can do about this.) -- Svein Willassen, ph.d. Tech Lead, appear.in
Received on Sunday, 5 January 2014 20:02:41 UTC