canmove, Confirmed users, Bureaucrats and Sysops emeriti
6,906
edits
m (→User stories) |
|||
Line 12: | Line 12: | ||
=== User stories === | === 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 | * 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 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 | * 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 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 | * 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. | ||
== UX design == | == UX design == |