Mobile/Projects/Screencasting: Project WebRTC video to second screen: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with "== 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 "projec...")
 
Line 10: Line 10:
* "Social" TV viewing: PIP of one or more video chats with your friends as you’re watching (yelling at the) TV together.
* "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.
* 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 so set up is easy and intuitive.
* 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 from my video call) and 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 social flow either within the room or over a video call.
* 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 social flow either within the room or over a video call.


== UX design ==
== UX design ==

Revision as of 15:49, 18 October 2013

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 on a second device.

Use cases & user stories

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 so set up is easy and intuitive.
  • 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 from my video call) and 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 social flow either within the room or over a video call.
  • 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 social flow either within the room or over a video call.

UX design

  • Not handed off yet

Quality criteria

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