Mobile/Projects/Screencasting: Project WebRTC video to second screen

Tracking

• Meta-bug to be filed

Goals

Develop initial multi-screen capabilities within Firefox, where content from one device (ie: phone or tablet) can be "projected" in a lightweight (possibly chromeless) browser window (or app?) on a second device.

Use cases & user stories

Example use cases

• Initiating and controlling a video call from a tablet, but having the incoming video displayed on the TV so the whole family can see. The "calling the grandparents" use case.
• "Social" TV viewing: PIP of one or more video chats with your friends as you’re watching (yelling at the) TV together.
• Send video to the big screen for group viewing (living room scenario), while controls remains on the smaller device.

User stories

• When I want to project something to a nearby (and compatible) screen, I want those devices to recognize each other as magically as possible and for set up to be as simple as possible, so setting up a device doesn't interrupt the flow of activity.
• When I want to project something to a nearby screen, I want the process to be as intuitive as possible -- for example: long-tapping an element on my handheld device (ie: the video window of my video call) and either selecting an item from a menu or flicking that element towards the screen in question -- so I don't have to spend a lot of time struggling with opening a session. Opening a projection should not interrupt the flow of activity.
• When I'm finished projecting to the larger screen, I want closing the projection to be as intuitive as possible so I don't get frustrated with the process or accidentally project more than intended to the screen. Closing a projection should not interrupt the flow of activity.
• When I am projecting something to a second screen, I want there to be as little chrome or browser-related UI to be on the large screen, so I am able to focus entirely on the content I'm interested in and that content is as large as possible.
• When I am projecting something to a second screen, I want that content to still be displayed on my handheld device as normal, so using and navigating that content isn't any different than it would be if I weren't projecting to the second screen.
• When I am projecting something to a second screen, I want to be able to control and manipulate that content as normal on my handheld device so using it is no different than it would be if I weren't projecting to the second screen.

UX design

• Not handed off yet

Quality criteria

• No user-perceptible performance degradation
• All goals are met
• All user stories are implemented & tested