Android will need to implement the Camera API UX/UI design. The UI spec is currently being created (with still image capture getting higher priority on the schedule) and will be attached when available. Feature page: https://wiki.mozilla.org/Platform/Features/Camera_API_-_Phase_2_%28getUserMedia%29

We need a UI to handle 1)asking the user permission to use his camera and/or his microphone 2)notify the user when the camera and/or microphone are on 3)provide status (of some sort) when the camera or microphone are "live" For security and privacy reasons, we can't trust the app to handle this for the user.

What's the difference in the use cases of this feature in FF Android in the browser vs. in a web app?

(In reply to Maire Reavy [:mreavy] from comment #1) > We need a UI to handle > 1)asking the user permission to use his camera and/or his microphone In the browser we typically use doorhangers for APIs that require permissions. For chromeless web apps we should perhaps use a different style of prompt; I don't know if we have already addressed this or have plans to address it. > 2)notify the user when the camera and/or microphone are on I'd suggest displaying a "toast" notification when the camera/microphone activates. > 3)provide status (of some sort) when the camera or microphone are "live" Many Android devices (like many laptops) have an LED to indicate camera status. To supplement this we can display a status message in the system notification bar -- though this (and any other screen area we would typically use for status messages) can be hidden by sites/apps that use the DOM full-screen API (mozRequestFullScreen).

For webapps I want to use the same doorhanger code, styled differently (bug 766300).

I suspect this comes with string changes, do we have someone to work on this?

UI work is happening over in bug 862377.