Mobile/Projects/Screencasting: Project WebRTC video to second screen
Jump to navigation
Jump to search
Rastreamento
- Meta-bug para ser aquivado
Talvez relacionado
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);
Objectivos
Melhorar as capacidades de multi-ecrã existente no Firefox, permitindo que o conteúdo WebRTC de um dispositivo (por exemplo: telefone ou tablet) seja "projetado" em uma (possivelmente sem cromo) janela com pouco peso do navegador (ou app)em um segundo dispositivo .
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.
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.
Technical specifications
- Should include both Roku and Chromecast support for casting
- Everything else: TBD
UX design
- Not handed off yet
- Related design doc: Firefox on TV Design Principles and Guidelines (P20-25 for design concepts)
- Related concepts:
- Mirrored display (what you see is what you show)
- Open local content from mobile device and show it on TV display (pairing to show local photos, videos, music in living room, might use location based sync, NFC, etc)
- Open online content on mobile and send it to TV display (showing online content like photos, videos, webpages, video calls, etc)
- Mobile as control device (while TV as display)
- Content (photos, videos) is shown on TV while control (zoom, pause) is shown on mobile
- Showing video call on TV (use TV display, camera & speaker while using mobile mic & control)
- Gaming, TV as display while playing game on mobile (consider also multi-player games)
- Co-watching a show
- Co-watching a show on two (or more) remote devices, co-watching while video calling
- Multiple input devices scenario (karaoke TV playlist)
- Create and share playlists with friends
- Mirrored display (what you see is what you show)
Justification
- Unique feature offering with strong user benefit.
Research & references
Quality criteria
- No user-perceptible performance degradation
- All goals are met
- All user stories are implemented & tested