Differences between revisions 6 and 37 (spanning 31 versions)
Revision 6 as of 2011-01-25 01:11:54
Size: 1928
Editor: eberkman
Comment:
Revision 37 as of 2011-01-27 21:11:53
Size: 12638
Editor: eberkman
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
== Story ==
Whether you’re a student in college, a design professional, or an author of a book, you have all experienced the clutter of notes, reminders, memos, drawings, and documents scattered across the surface of your desk. There comes a point in this chaotic, unorganized display, when your tidy instinct begs for some order.
== What a Mess! ==
Whether you’re a student in college, a design professional, or an author of a book, you have all experienced the clutter of notes, reminders, memos, drawings, and documents scattered across the surface of your desk. There comes a point in this chaotic, unorganized display, when your tidy instinct begs for some order.  
Line 4: Line 4:
If your lucky, you quickly find materials you can use: a binder, file folders with the colored tabs, paper clips, even a stapler. You initially grab the content, sort and filter as a means for organizing and making order. As you organize, you may classify the data by such relationships as (see Chapter 3, [[Display of Information]]): If your lucky, you quickly find materials you can use: a binder, file folders with the colored tabs, paper clips, even a stapler. You grab the content, sort and filter as a means for organizing and making order. As you organize, you may classify the data by such lateral relationships as (see Chapter 3, [[Display of Information]]):

 * '''Nominal''' - uses labels and names to categorize data.
 * '''Ordinal''' - using numbers to order things in sequence.
 * '''Alphabetical''' - using the order of the alphabet to organize nominal data.
 * '''Geographical''' - using location, such as city, state, country, to organize data.
 * '''Topical''' - organizing data by topic or subject.
 * '''Task''' - organizing data based on processes, tasks, functions and goals.

Having now integrated your organizational skills with those office supplies, you can marvel at the clean desk. On its surface lay a faceted arrangement of folders. Each folder, containing related content, is clearly labeled with colored tabs housing to allow for quick and easy access.

== Navigation Structure ==
As discussed in Chapter 3, [[Display of Information]], we understand the importance of organizing an information structure across a single page, or an entire OS. To recap, we know that are two main types of organizing with information architecture.
 * '''Hierarchy''' – which organizes content based on top-down, parent-child relationships.
 * '''Faceting'''- organizes based on information attributes without the parent-child relationships. The structure is based on heterogeneous content, that share the same level within an information architecture.

== Lateral Access and the Mobile Space ==
Content across device’s OS must be organized and designed to follow a consistent information architecture to ensure a positive user experience. However, when considering mobile devices, the potentially smaller displays play a significant role in determining how this information architecture is designed for interaction. Smaller screen sizes affect the amount and type of content presented, and the user’s ability to successfully search, select, and read this information. To account for this, consider presenting the information laterally (at the same level tier in the information architecture) with appropriate widgets of access.

=== Reasons to Use Lateral Access Widgets Across the Mobile Space: ===
 * Mobile displays can be much smaller than a PC, reducing the amount of information shown on a viewport’s current state. Unlike PCs, where information is designed for a 1024x 768 resolution, common smartphones have screen resolutions at 320x480px.
 * Globally, feature phones still make up about 80% of the mobile market. These devices have a common resolution of 240 x 320px, though some can have smaller screen resolutions down to 128 x 176px.
 * Because the screen real estate is so valuable, it’s important to prioritize features and content related to the user’s high-level goals.
 * A mobile user’s attention is competing with all of the stimuli in the surrounding environment. Therefore, the access to the content must be detectable and afford its function appropriately.
 * According to [[http://en.wikipedia.org/wiki/Fitts%27s_law|Fitts’ Law]], there is a direct correlation between the size of the target, its distance from the user, and the amount of time it takes to select it. Therefore, a smaller display requires larger buttons for gestural interaction. Which, in effect, will reduce the amount of content that can be placed on the screen.
  
=== Benefits of lateral Access ===
 * Limits the amount of levels to access priority information.
 * Reduces the amount of clicking and/or selecting
 * Reduces the exiting or opening of pages.
Line 7: Line 36:
== Follow the Principles of Wayfinding and Norman’s Interface Model ==
As you know are now aware, the size of mobile displays can greatly influence how your content should be organized and designed. To make sure your user’s can navigate across this content, consider applying researched-based frameworks tied to wayfinding and Donald Norman’s Interaction model.
=== Wayfinding ===
In the introduction to the [[Widget]] part, the principles of wayfinding are discussed in detail. Certain wayfinding principles can be applied to lateral access widgets to ensure your user can navigate across content with ease.
 * '''Districts''': Within the viewport, sections of information that are grouped or bounded by visual elements that follow the laws of proximity will be perceived as being related and separate from other components.
  * Tabs – place related tabs adjacent to each other to define a perceived group. These tabs may share common visual design elements, such as size, shape, color, and form. If you are using multiple groups of tabs, make sure these are clearly distinguishable from other tab groups. Selected tabs must be bound to the related area of content.
  * Pagination controls and Indicators – Most often these widgets should be placed immediately above and below the content unique to the page. Another option is to anchor the widget (in the title bar, for example), so it is available at all points on the page. If the page does not scroll, a single fixed-location item logically becomes an anchored widget.
Line 8: Line 44:
 * '''Landmarks''': Distinct visual objects that are easily detected and identified from other elements, will likely be perceived as reference points. In the mobile space, using landmarks can aid the user in quickly finding key navigation features, as well as providing a reference to their position within the browsable content. When designing lateral access widgets as landmarks, consider shapes that are well understood by the user and afford the correct action.
== Norman’s Interface Model ==
As Donald Norman would say, “Make things visible!” Lateral access elements must follow the principles of legibility, readability, and conspicuity discussed throughout this book.
Line 9: Line 48:
Consider the following principles:
Line 10: Line 50:
=== Feedback ===
Feedback is a noticeable, and immediate response to a direct interaction. Using feedback appropriately confirms to the user that his action took place. Feedback can be visual, haptic, and audible. If feedback is too delayed, or does not exist, the user will become frustrated or lost after the action is completed.
Lateral access widgets should use feedback that immediately follows the action.
Line 11: Line 54:
Consider how feedback can be applied to:
Line 12: Line 56:
 * Tabs – An immediate response must occur after a user selects tabs. The selected tab may change color and size and will display its related content in the viewport. Adjacent tabs that are not selected must remain unaffected. Be sure to follow conspicuity guidelines when selecting appropriate colors to contrast with the background.
 * Simulated 3D Effects – Whether you are peeling a back corner to reveal the page underneath, or rotating an object, feedback must occur to indicate the action was successful. As discussed in detail in the Components part, images are transformed incrementally within our visual perception process. When we see an object move and transform its shape in incremental steps, we have an easier time understanding that the two objects are related or identical. Therefore, use appropriate transition speeds throughout the entire action.
 * Pagination – Feedback can be used to display indications of page jump. Those pages not accessible due to current context can be greyed out. For example "Back" or "First page" links should be visible but inaccessible when already on the first page.

=== Mapping ===
Mapping describes the relationship between two objects and how well we understand their connection. We’re able to create this relationship when we combine the use of our prior knowledge with our current behaviors. To quickly recall these relationships, we develop cognitive heuristics, or cultural metaphors. These metaphors reinforce our understanding of the relationship of object and its function.

Some common metaphors you can use to access information on mobile devices are:

 * '''Tabs''' - are understood in principle to the file folder tab. We expect this tab to be selectable and an identifier of a folder that contains related content. If we see one tab, we will expect to see adjacent tabs that are separating additional content. Too many grouped tabs; however, will cause our users to become cognitively overloaded during the decision making process. Thus, resulting in slower performance and user frustration.
 * '''Cubes''' – show content on one or two faces, and will be expected to have content on all other sides that share the same axis. Users will expect faces to rotate. Constrain the rotation to one axis, otherwise users will become frustrated with the inability to quickly navigate and correctly select the content. Animation of the rotation from one face to the other must be provided. Otherwise, the user may not know their current selection’s position on the cube.
 * '''Peeled Corners'''- pages that are slightly peeled back are understood in principle to pages in a book. We expect access to the pages underneath the top layer. A gestural interaction that allows for turning the page will be expected. Animate the transition from one page to the next.
 * '''3D effects''' - such as shadows and transparency can be used to simulate layers and depth. The user will understand that information can occupy virtual space, appearing modally in front of other layers, while hiding others.

'''Constraints'''
 
Restrictions on behavior should be appropriately implemented to eliminate or reduce performance error while laterally accessing content. Consider using the boundaries of the display (edges and corners) during gestural and scroll and select navigation. The edges and corners provide an infinite area to move our fingers or curser over. This can significantly reduce the amount of time to navigate across pages. Consider this effect when using a circular or closed navigation structure.
 * '''Circular navigation''' - A key tactical consideration, mentioned several times in the patterns, is whether browsable data sets are circular or dead end. Circular lists simply go around and around. When at the "last" item in a list, continuing to view the next item will display the first one in the list. This is useful for faceted views, or other cases where the ordering is unimportant. Consider integrating the [[Location Within]] widget to indicate current position.
 * '''Closed navigation''' - For dead end lists, there is a definitive start and stop, and (aside from links such as "back to top") there is no way to go to the other end. These are useful for information with a very ordered, single-axis display. Most hierarchies, and much date-sorted information should display like this. Such as a message list that starts with the most recent. Consider integrating the [[Pagination]] widget to indicate current position.

 

What a Mess!

Whether you’re a student in college, a design professional, or an author of a book, you have all experienced the clutter of notes, reminders, memos, drawings, and documents scattered across the surface of your desk. There comes a point in this chaotic, unorganized display, when your tidy instinct begs for some order.

If your lucky, you quickly find materials you can use: a binder, file folders with the colored tabs, paper clips, even a stapler. You grab the content, sort and filter as a means for organizing and making order. As you organize, you may classify the data by such lateral relationships as (see Chapter 3, Display of Information):

  • Nominal - uses labels and names to categorize data.

  • Ordinal - using numbers to order things in sequence.

  • Alphabetical - using the order of the alphabet to organize nominal data.

  • Geographical - using location, such as city, state, country, to organize data.

  • Topical - organizing data by topic or subject.

  • Task - organizing data based on processes, tasks, functions and goals.

Having now integrated your organizational skills with those office supplies, you can marvel at the clean desk. On its surface lay a faceted arrangement of folders. Each folder, containing related content, is clearly labeled with colored tabs housing to allow for quick and easy access.

As discussed in Chapter 3, Display of Information, we understand the importance of organizing an information structure across a single page, or an entire OS. To recap, we know that are two main types of organizing with information architecture.

  • Hierarchy – which organizes content based on top-down, parent-child relationships.

  • Faceting- organizes based on information attributes without the parent-child relationships. The structure is based on heterogeneous content, that share the same level within an information architecture.

Lateral Access and the Mobile Space

Content across device’s OS must be organized and designed to follow a consistent information architecture to ensure a positive user experience. However, when considering mobile devices, the potentially smaller displays play a significant role in determining how this information architecture is designed for interaction. Smaller screen sizes affect the amount and type of content presented, and the user’s ability to successfully search, select, and read this information. To account for this, consider presenting the information laterally (at the same level tier in the information architecture) with appropriate widgets of access.

Reasons to Use Lateral Access Widgets Across the Mobile Space:

  • Mobile displays can be much smaller than a PC, reducing the amount of information shown on a viewport’s current state. Unlike PCs, where information is designed for a 1024x 768 resolution, common smartphones have screen resolutions at 320x480px.
  • Globally, feature phones still make up about 80% of the mobile market. These devices have a common resolution of 240 x 320px, though some can have smaller screen resolutions down to 128 x 176px.
  • Because the screen real estate is so valuable, it’s important to prioritize features and content related to the user’s high-level goals.
  • A mobile user’s attention is competing with all of the stimuli in the surrounding environment. Therefore, the access to the content must be detectable and afford its function appropriately.
  • According to Fitts’ Law, there is a direct correlation between the size of the target, its distance from the user, and the amount of time it takes to select it. Therefore, a smaller display requires larger buttons for gestural interaction. Which, in effect, will reduce the amount of content that can be placed on the screen.

Benefits of lateral Access

  • Limits the amount of levels to access priority information.
  • Reduces the amount of clicking and/or selecting
  • Reduces the exiting or opening of pages.

Follow the Principles of Wayfinding and Norman’s Interface Model

As you know are now aware, the size of mobile displays can greatly influence how your content should be organized and designed. To make sure your user’s can navigate across this content, consider applying researched-based frameworks tied to wayfinding and Donald Norman’s Interaction model.

Wayfinding

In the introduction to the Widget part, the principles of wayfinding are discussed in detail. Certain wayfinding principles can be applied to lateral access widgets to ensure your user can navigate across content with ease.

  • Districts: Within the viewport, sections of information that are grouped or bounded by visual elements that follow the laws of proximity will be perceived as being related and separate from other components.

    • Tabs – place related tabs adjacent to each other to define a perceived group. These tabs may share common visual design elements, such as size, shape, color, and form. If you are using multiple groups of tabs, make sure these are clearly distinguishable from other tab groups. Selected tabs must be bound to the related area of content.
    • Pagination controls and Indicators – Most often these widgets should be placed immediately above and below the content unique to the page. Another option is to anchor the widget (in the title bar, for example), so it is available at all points on the page. If the page does not scroll, a single fixed-location item logically becomes an anchored widget.
  • Landmarks: Distinct visual objects that are easily detected and identified from other elements, will likely be perceived as reference points. In the mobile space, using landmarks can aid the user in quickly finding key navigation features, as well as providing a reference to their position within the browsable content. When designing lateral access widgets as landmarks, consider shapes that are well understood by the user and afford the correct action.

Norman’s Interface Model

As Donald Norman would say, “Make things visible!” Lateral access elements must follow the principles of legibility, readability, and conspicuity discussed throughout this book.

Consider the following principles:

Feedback

Feedback is a noticeable, and immediate response to a direct interaction. Using feedback appropriately confirms to the user that his action took place. Feedback can be visual, haptic, and audible. If feedback is too delayed, or does not exist, the user will become frustrated or lost after the action is completed. Lateral access widgets should use feedback that immediately follows the action.

Consider how feedback can be applied to:

  • Tabs – An immediate response must occur after a user selects tabs. The selected tab may change color and size and will display its related content in the viewport. Adjacent tabs that are not selected must remain unaffected. Be sure to follow conspicuity guidelines when selecting appropriate colors to contrast with the background.
  • Simulated 3D Effects – Whether you are peeling a back corner to reveal the page underneath, or rotating an object, feedback must occur to indicate the action was successful. As discussed in detail in the Components part, images are transformed incrementally within our visual perception process. When we see an object move and transform its shape in incremental steps, we have an easier time understanding that the two objects are related or identical. Therefore, use appropriate transition speeds throughout the entire action.
  • Pagination – Feedback can be used to display indications of page jump. Those pages not accessible due to current context can be greyed out. For example "Back" or "First page" links should be visible but inaccessible when already on the first page.

Mapping

Mapping describes the relationship between two objects and how well we understand their connection. We’re able to create this relationship when we combine the use of our prior knowledge with our current behaviors. To quickly recall these relationships, we develop cognitive heuristics, or cultural metaphors. These metaphors reinforce our understanding of the relationship of object and its function.

Some common metaphors you can use to access information on mobile devices are:

  • Tabs - are understood in principle to the file folder tab. We expect this tab to be selectable and an identifier of a folder that contains related content. If we see one tab, we will expect to see adjacent tabs that are separating additional content. Too many grouped tabs; however, will cause our users to become cognitively overloaded during the decision making process. Thus, resulting in slower performance and user frustration.

  • Cubes – show content on one or two faces, and will be expected to have content on all other sides that share the same axis. Users will expect faces to rotate. Constrain the rotation to one axis, otherwise users will become frustrated with the inability to quickly navigate and correctly select the content. Animation of the rotation from one face to the other must be provided. Otherwise, the user may not know their current selection’s position on the cube.

  • Peeled Corners- pages that are slightly peeled back are understood in principle to pages in a book. We expect access to the pages underneath the top layer. A gestural interaction that allows for turning the page will be expected. Animate the transition from one page to the next.

  • 3D effects - such as shadows and transparency can be used to simulate layers and depth. The user will understand that information can occupy virtual space, appearing modally in front of other layers, while hiding others.

Constraints

Restrictions on behavior should be appropriately implemented to eliminate or reduce performance error while laterally accessing content. Consider using the boundaries of the display (edges and corners) during gestural and scroll and select navigation. The edges and corners provide an infinite area to move our fingers or curser over. This can significantly reduce the amount of time to navigate across pages. Consider this effect when using a circular or closed navigation structure.

  • Circular navigation - A key tactical consideration, mentioned several times in the patterns, is whether browsable data sets are circular or dead end. Circular lists simply go around and around. When at the "last" item in a list, continuing to view the next item will display the first one in the list. This is useful for faceted views, or other cases where the ordering is unimportant. Consider integrating the Location Within widget to indicate current position.

  • Closed navigation - For dead end lists, there is a definitive start and stop, and (aside from links such as "back to top") there is no way to go to the other end. These are useful for information with a very ordered, single-axis display. Most hierarchies, and much date-sorted information should display like this. Such as a message list that starts with the most recent. Consider integrating the Pagination widget to indicate current position.

Patterns for Lateral Access

Using appropriate and consistent lateral access widgets will provide an alternative way to present and manipulate content serially. Within this chapter, the following patterns will be discussed, based on how the human mind organizes and navigates information:

  • Tabs– Based on the concept of file folder tabs, these elements are used to separate and clearly communicate, sets of pages or features at the same level in the information architecture.

  • Peel Away – An organic and animated representation of a page being flipped over to reveal a second page behind it.

  • Simulated 3D Effects – Displays and alternate view to the content on the page using 3D graphics. When device gestures or viewer movements are used, these items affected will follow the presumed physics or correctly represent the space they occupy.

  • Pagination –Serially displays a location within a set of pages. Offers the ability and function to navigate between pages easily and quickly.

  • Location Within –An indicator is required to show the current page location within series of several screens of similar or continuous information. This is presented with an organic access method.

Lateral Access (last edited 2011-12-13 06:24:53 by shoobe01)