Originally posted on VoIP & Gadgets Blog, here: http://blog.tmcnet.com/blog/tom-keating/webrtc/webrtc-challenges.asp.
WebRTC holds a lot of promise, and with the buzz surrounding WebRTC beginning to reach a fever pitch, it's worth pointing out the challenges facing WebRTC.
The growth of mobile platforms made the demand for H.264 support even more acute: hardware acceleration of H.264 decompression is all but universal on mobile devices and taking advantage of this hardware support is essential for providing acceptable battery life.
This seems to confirm my suspicions, that Google worrying about WebRTC developers having to pay H.264 royalty fees is unwarranted, but again if I am wrong, please post a comment.
Really That's your rationale for not support full desktop sharing You're worried about an embarrassing popup as well as the presence of desktop icons It sounds like an excuse. Google tends to be web-centric (Gmail, Chrome, YouTube, etc.) and this comment to me seems to me like Google dismisses the value of the local desktop. Sorry Google, but not everything runs in the Web, as much as you would like it to.
The W3C Last Call Working Draft is expected in Q3 2013, with the final WebRTC specification expected to be standardized in 2014. So we're still a ways off from WebRTC becoming finalized, but as with anything this exciting in technology, developers are itching to write WebRTC applications today. Just keep your pants on if everything doesn't go as expected and make sure you attend the WebRTC Conference & Expo taking place June 25-27th in Atlanta! I'll definitely be there.
Tags: apple, challenges, chrome, codecs, firefox, google, h.264, internet explorer, microsoft, safari, screen sharing, skype, vp8, webrtc
Related tags: voice video, entire desktop, screen sharing, desktop sharing, webrtc conference, webrtc
Google Reader Profile