Media/getUserMedia: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 46: Line 46:
== Phase 3 ==
== Phase 3 ==
* Implement permissions, notification & status UI
* Implement permissions, notification & status UI
** Android: bug ???
** Android: {{bug|749881}}
** B2G: bug ???
** B2G: {{bug|749882}}
** Desktop: {{bug|729522}} [???]
** Desktop: {{bug|729522}} and {{bug|748835}} -- since the camera/mic UI for WebRTC and Camera API are becoming almost the same, these bugs may now be duplicates [???]


Once UI lands, getUserMedia may be pref'ed on.
Once UI lands, getUserMedia may be pref'ed on.

Revision as of 23:45, 10 May 2012

getUserMedia Implementation Roadmap

Goal

  • Implement the getUserMedia specification on 3 platforms: Desktop, Android and B2G.
  • Includes the following uses of getUserMedia:
  getUserMedia({picture:true}, onsuccess(Blob blob), onerror);
  getUserMedia({video:true,audio:true}, onsuccess(MediaStream stream), onerror);
  video.src = stream;
  audio.src = stream;
  • Appropriate permission, notification and status UIs.

Phase 1

  • Define common abstraction "MediaEngine" for device access across multiple platforms.
  • Implement a fallback backend for MediaEngine (when hardware support not available, returnMediaStream with white noise, for example).
  • Write DOM bindings for getUserMedia (backed with Fallback MediaEngine).

Phase 2

  • Implement MediaEngine backends:
    • Android: bug ??? (either based on Android NDK/SDK, or, webrtc.org code).
    • B2G: bug ??? [Fabrice] (based on Gonk).
    • Desktop: bug 691234 [Anant] (based on webrtc.org code).
  • Implement image capture {picture:true} API

Phase 3

  • Implement permissions, notification & status UI

Once UI lands, getUserMedia may be pref'ed on.

Phase 4 and beyond

  • Implement file backend for MediaEngine.
  • Refactor getUserMedia{picture:true} implementations to use MediaEngine + privileged MediaStreams and CameraControl APIs.