Yesterday, Opera announced and released the latest version of its mobile browser, Opera Mobile 12. Today, while running the browser against the Ringmark suite, I noticed that it was now passing the WebRTC detection tests. Very exciting, indeed!
To test drive the first ever mobile browser implementation of WebRTC, I decided to use dmv — my super simple Node.js served, socket.io enabled, navigator.getUserMedia normalized, video-frame-to-canvas capturing program, which was developed using an Opera Labs build and Google Chrome Canary for desktop.
The following video demonstrates Opera Mobile 12 using the Nexus One’s built in camera, piping a url object to a HTML5 video element node, while the frames are read and drawn to a canvas element at ~30fps:
If your browser is from 1977 and the above video doesn’t work, try watching it on Youtube.
Comments
We moved off of Disqus for data privacy and consent concerns, and are currently searching for a new commenting tool.
Awesome!
Augmented reality in the browser. We’re almost there!
Fake.
No, it’s not. This has been possible with Opera’s Labs build for months.\u00a0
boot2opera?
Sadly, there is no PeerConnection support, which in my opinion is the more important component of WebRTC.
Additionally, no vendor has released a browser, mobile or otherwise, that supports multiple PeerConnection objects on a page. It’s unfortunate, I have an app that would be very neat, but it’s currently useless. :[ Oh well, patience is the name of the game.
That’s amazing!
Kudos to the Opera crew 🙂
Damn you, Rick, you magnificent bastard!
Nice! Here’s my demo app called Webcam Toy: http://neave.com/webcam/html5/ It uses getUserMedia/WebRTC and works in Opera Mobile 12 for Android 🙂
very cool to see device features like a camera interacting directly with a browser
To reiterate what others have said: this is getUserMedia support, not WebRTC support. The missing part is peer-to-peer communication, i.e. PeerConnection. Without that, there’s Web but no RTC!
ok