Interaction patterns


Published on

Interaction patterns , VS2012 Design For Usability

Published in: Internet, Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Interaction patterns

  1. 1. Faisal Imran
  2. 2. About VS 2012  Visual Studio is a comprehensive collection of tools and services to help you create a wide variety of apps, both for the Microsoft platform and beyond.  Visual Studio also connects all of your projects, teams, and stakeholders. Now your team can work with greater agility from virtually anywhere—irrespective of development tool, including Eclipse and Xcode.  Whether you’re designing mission-critical .NET apps, writing blazing fast code with C++ AMP, or testing and debugging a cloud-connected HTML/JavaScript app that runs on many devices, join millions of developers worldwide in choosing Visual Studio as your essential development environment.
  3. 3. 1. Wizard  Usability Principle User Guidance (Visibility)
  4. 4. 2. Grid Layout  Usability Principle Consistency, Predictability (Conceptual Models)  Context Any circumstance where several information objects are presented and arranged spatially on a limited area. Typically in the design of dialog screens, forms and web pages.
  5. 5. 3. Progress  Usability Principle Guidance (Feedback)  Context Systems tasks that take a long time (typically more than a few seconds) and must be completed before the next tasks can be started.
  6. 6. 4. Shield  Usability Principle Error Management (Safety)  Context Functions that have irreversible (side) effects or require a lot of resources to undo/reverse. The (side) effects may lead to unsafe or highly undesired situations. Often it is the combination of action arguments that makes it severe, and the user may not be aware of this, since it is normally safe.
  7. 7. 5. Preferences  Usability Principle Adaptability (Flexibility)  Context The application is very complex and many of its functions can be tuned to the user’s preference. Not enough is known about the user's preferences in order to assume defaults that will suit all users. The potential users can range from novice to expert.
  8. 8. 6. Contextual Menu  Usability Principle User Guidance (Visibility)  Context An application typically contains a lot of functionality and the user needs to know her possibilities at any point during use.
  9. 9. 7. Focus  Usability Principle Guidance (Constraints)  Context An application where several visual objects are manipulated, typically drawing packages or browsing tools.
  10. 10. 8. Unambiguous Format  Usability Principle User Guidance (Constraints)  Context Any system where structured data must be entered. Data such as dates, room numbers, social security numbers or serial numbers are usually structured. The exact syntax used for such data may vary per country or product.  Date Time Selection is example in VS2012
  11. 11. 9. Navigating between Spaces  Usability Principle User Guidance (Natural Mapping)  Context Systems with a lot of states, functionality and objects, that are relevant only in groups.
  12. 12. 10. Preview  Usability Principle Compatibility (Natural Mapping)  Context In many applications the user needs to find an item e.g. a file, a presentation, video clip, or an image, for which a visual or auditory search criterion is more effective but the index of the set is not audiovisual (e.g. a text label).
  13. 13. 11. Favourites  Usability Principle Minimizing Actions (Flexibility)  Context The user is looking for an item that is contained in a large set of items. The item is of importance and the user requires it regularly. Items are typically files, colors, web pages or database records and are part of large collections, respectively a file system, the web or a Database.
  14. 14. 12. Container Navigation  Usability Principle Grouping of Elements (Natural Mapping)  Context Many applications contain aggregated data, which the user must browse through. Quite often, the user wants to invoke a function taking one of the parts as input parameter.
  15. 15. 13. Setting Attributes  Usability Principle User Guidance (Visibility)  Context In many applications, a document can hold many different objects with many different attributes
  16. 16. 14. Warning  Usability Principle Error prevention (Safety)  Context Situations where the user performs an action that may unintentionally lead to a problem