Differences between revisions 5 and 6
Revision 5 as of 2011-04-15 04:38:03
Size: 3059
Editor: eberkman
Comment:
Revision 6 as of 2011-04-16 04:11:23
Size: 5325
Editor: eberkman
Comment:
Deletions are marked like this. Additions are marked like this.
Line 25: Line 25:

== Pattern Table Chapter 4 ==
=== Chapter 6: Lateral Access ===
||'''Pattern'''||'''Design Problem'''||'''Solution''' ||'''Other Patterns to Reference'''||
||'''[[Tabs]'''||Access must be provided to a small number of items at the same level in the information architecture, while also clearly communicating this hierarchy of information. ||Follow the file folder metaphor by creating distinct labels that separate 3-8 sets of content.||[[Titles]], [[Pagination]], [[Location Within]]||
||[[Peel Away]]||A method must be provided to confirm only authorized individuals have access to a device, or a site, service or application on the device.||Consider whether your specific situation requires explicit authentication. Mobiles should only require authentication for first time entry, or for very high security situations. Mobile-like multi-user devices such as kiosks will also require authentication.||[[Pop-Up]], [[Drag]], [[Input Areas]], [[Titles]]||
||[[Simulated 3D Effects]]||Exiting a screen, process or application could cause a catastrophic (unrecoverable) loss of data, or a break in the session.||Present a modal dialogue which delays the user from exiting immediately (the app or function is kept open in the background), informs them of the consequences of exiting (loss of data) and requires them to make choices, at least confirm exit or return to session.||[[Wait Indicator]], [[Pop-Up]], [[Titles]]||
||[[Pagination]||User entered data or subsidiary processes would be time consuming, difficult or frustrating to reproduce if lost due to accidental user-selected destruction.||Processes must be designed to protect user input. Methods must be provided to recover previous and historical entry.||[[Clear Field]], [[Autocomplete]], [[Hierarchical List]], [[Input Areas]]||
||[[Location Within]]||High security systems or those which are publicly accessed and are likely to be heavily shared (such as kiosks), must have a timer to exit the session and/or lock the system after a period of inactivity.||Try to avoid the use of timeout as a solution to load and security. If sessions must expire due to the method by which they have been built already, consider making this transparent.||[[Pop-Up]], [[Sign-On]], [[Exit Guard]], [[Titles]]||

Wrap Up

As we’ve just seen, mobile widgets are highly reusable items and used repeatedly, across the device’s OS. These widgets are always-on, internet-connected, auto-updated, lightweight applications and appear as miniaturized display elements within an existing or enclosing GUI. Widgets can be used to quickly access related levels of information, provide visual cues about the current state of the device, and control the amount of information and level of detail needed on a page. When incorporating these component patterns into your design, consider:

  • Widget information must be immediately visible and contextual.
  • Using a stepped portlet approach to reveal levels of information.
  • Following wayfinding principles throughout navigation.
  • The appropriate use of color coding and labeling in its design.

Chapter 6: Lateral Access

This chapter explained how lateral access widgets assist the user in quickly navigating to and accessing same level tier content. This is especially important on mobile devices because the potentially smaller screen sizes affect the amount and type of content presented, and the user’s ability to successfully search, select, and read this information.

Chapter 7: Drill Down

In this chapter you learned that drilldown widgets are used to support many functions that contain parent-child relationships. These widgets can be used in any context to provide access to related content, allow the user to submit information, create a change in the current state of the device, and provide related information in a glanceable manner. Drilldown widgets support the parent-child information architecture relationship.

Chapter 8: Labels & Indicators

In some situations, it may be required to use small labels, indicators and other additional pieces of information to describe content. Mobile users each have unique goals. Some require instant additional information without clicking. Others may need additional visual cues to assist them while quickly locating information. In any case, the information labels must be presented appropriately while considering valuable screen real estate, cultural norms and standards.

Chapter 9: Information Controls

This chapter explained that finding specific items within a long list or other large page or data array can be challenging which impacts the user experience. Information control widgets are used to locate specific information quickly.

Pattern Reference Chart

This pattern reference chart lists all of the patterns found within each chapter described in this part of the book. Each pattern has a general description of how it can apply to a design problem while offering a broad solution.

Cross-referencing patterns are common throughout this book. Design patterns often have variations in which other patterns can be used due to the common principles and guidelines they share. These cross-referenced patterns are listed along with the page number where they are fully described in this book.

Pattern Table Chapter 4

Chapter 6: Lateral Access

Pattern

Design Problem

Solution

Other Patterns to Reference

[[Tabs]

Access must be provided to a small number of items at the same level in the information architecture, while also clearly communicating this hierarchy of information.

Follow the file folder metaphor by creating distinct labels that separate 3-8 sets of content.

Titles, Pagination, Location Within

Peel Away

A method must be provided to confirm only authorized individuals have access to a device, or a site, service or application on the device.

Consider whether your specific situation requires explicit authentication. Mobiles should only require authentication for first time entry, or for very high security situations. Mobile-like multi-user devices such as kiosks will also require authentication.

Pop-Up, Drag, Input Areas, Titles

Simulated 3D Effects

Exiting a screen, process or application could cause a catastrophic (unrecoverable) loss of data, or a break in the session.

Present a modal dialogue which delays the user from exiting immediately (the app or function is kept open in the background), informs them of the consequences of exiting (loss of data) and requires them to make choices, at least confirm exit or return to session.

Wait Indicator, Pop-Up, Titles

[[Pagination]

User entered data or subsidiary processes would be time consuming, difficult or frustrating to reproduce if lost due to accidental user-selected destruction.

Processes must be designed to protect user input. Methods must be provided to recover previous and historical entry.

Clear Field, Autocomplete, Hierarchical List, Input Areas

Location Within

High security systems or those which are publicly accessed and are likely to be heavily shared (such as kiosks), must have a timer to exit the session and/or lock the system after a period of inactivity.

Try to avoid the use of timeout as a solution to load and security. If sessions must expire due to the method by which they have been built already, consider making this transparent.

Pop-Up, Sign-On, Exit Guard, Titles

Widget Wrapup (last edited 2011-12-13 16:58:09 by shoobe01)