Confirmed users
1,492
edits
Mobile/UI/Designs/TouchScreen/workingUI: Difference between revisions
Jump to navigation
Jump to search
Mobile/UI/Designs/TouchScreen/workingUI (view source)
Revision as of 17:06, 30 October 2008
, 30 October 2008→Working Mockups - large-format screen (e.g. n810, android, iphone)
No edit summary |
|||
| Line 38: | Line 38: | ||
http://people.mozilla.com/~madhava/files/mobile/2008-06-26/basic4.png | http://people.mozilla.com/~madhava/files/mobile/2008-06-26/basic4.png | ||
=== Panning and Zooming === | |||
==== Panning ==== | |||
* linear panning when the user is in contact with the screen | |||
* when the user "flicks" or "swipes" the screen pans kinetically | |||
** distance and speed traveled corresponds to the vigor of the flick | |||
** a flick at the most-vigorous end of the spectrum should allow the user to reach the left or right side of the page in one flick | |||
** when the page is scrolling by with the user _not_ in contact with the screen (ie. during a flick), the user should be able to stop page movement by tapping the screen (pinning the page down, essentially) | |||
* we should constrain movement so that minor variances from an otherwise straight-line pan do not cause much jitter | |||
==== Zooming ==== | |||
'''Structured Zoom''' | |||
The primary zooming mechanism is double-tapping on a page element (column, image, other area) and having the page zoom to fit that particular element. This will involve some rules for different circumstances -- for example, the appropriate zoomed-in level for an image is probably to do a best fit, horizontally and vertically, so that the _whole_ image is as large as it can be on the screen; in contrast, the best zoomed-in level for a column of text is probably to fit horizontally only. Double-tapping again should zoom the user back out to the original page overview zoom level. | |||
This is the primary scheme because it takes advantage of the fact that, generally, webpages have structure that corresponds to what a user is likely interested in. Structured zoom will be more often useful than arbitrary zoom. | |||
That said, some mechanism for arbitrary zoom is still necessary for cases where this breaks down (e.g. zooming within an image). | |||
'''Arbitrary Zoom''' | |||
Arbitrary zoom is the case where the user wants to zoom in to a level that is not related to the edges of an element. | |||
There are two parts to the information that a user has to provide in this case -- (1) how much to zoom in (or out) and (2) where to zoom in to (i.e. what is the centre of the zoom). Some interaction mechanisms let the user communicate both at the same time (the pinch gesture in a multitouch environment), others don't (choosing a zoom percentage from a list). One that addresses both would be better for Fennec. | |||
1. Multitouch | |||
2. Successive touch (pseudo-multitouch) -- i.e. defining corners of a desired range with two fingers tapped in quick succession. | |||
3. Gesture - "dialing" clockwise to zoom in, counterclockwise to zoom out -- see http://socialhelix.com/ for an example. | |||
3. Tracing the area to zoom in to | |||
=== Controls === | === Controls === | ||
| Line 178: | Line 213: | ||
Working here: [[Mobile/UI/Designs/TouchScreen/workingUI/desktop_integration]] | Working here: [[Mobile/UI/Designs/TouchScreen/workingUI/desktop_integration]] | ||
==Working Mockups - small-format screen (e.g. windows mobile)== | ==Working Mockups - small-format screen (e.g. windows mobile)== | ||