IFD:Course Interaction Design: Difference between revisions

IFD:Course Interaction Design (view source)

Revision as of 11:15, 18 November 2010

380 bytes added , 18 November 2010

→‎Feedback

JanD

Bureaucrats, emailconfirmed

1,221

edits

@@ Line 380: / Line 380: @@
 ===Feedback===
 [[File:746px-Eric_'slowhand'_Clapton.jpg|thumb|200px|Could Eric Clapton play guitar without feedback? Probably not!]]
-While visibility ensures that users easily know what you can be done, offering feedback ensures that users know which results their actions have.
+While visibility ensures that users easily know what you can be done, offering immediate feedback ensures that users know which results their actions have.
-Feedback is a well known real world experience. When you cut bread you know see the knife moving and feel the change resistance. When you play an instrument you experience that a movement of you hand immediately changes the sound.
+Feedback is a well known real world experience.  When you play an instrument you experience that a movement of you hand immediately changes the sound.
-Imagine you would not have feedback in the above examples: Having no resistance and visibility of the knife while cutting bread would cause you carrying on with slicing the table after the bread is done. If you would need to play guitar without hearing the sound you would need to check afterwards if you got it right.
+<!--When you cut bread you know see the knife moving and feel the change resistance. Imagine you would not have feedback in the above examples: Having no resistance and visibility of the knife while cutting bread would cause you carrying on with slicing the table after the bread is done.-->
+Imagine you would need to play guitar without hearing the sound! You would need to check afterwards if you got it right and would have no opportunity to improve while playing and listening.
 [[File:Progress_bar_gnome_ubuntu.png|thumb|200px|a widget dedicated to feedback: the progressbar]]
-Ideally feedback is immediate and and directly visible. Feedback seems to be such an basic experience that everybody is confused if there is no feedback within a few moments. Without feedback people often start pushing buttons many times or they assume that the system has crashed, though it may just be busy doing what the user wants. To prevent this confusion an widget called "progessbar" is very useful. It is often seen when copying bigger amounts of data from one place to another. The movement of the progressbar shows that the computer works.
+Ideally feedback is immediate and and directly visible. Feedback seems to be such an basic experience that everybody is confused if there is no feedback within a few moments. Without feedback people often start pushing buttons many times or they assume that the system has crashed, though it may just be busy doing what the user wants. To prevent this confusion an widget called "progessbar" is very useful. It is often seen when copying bigger amounts of data from one place to another. The movement of the progressbar shows that the computer works.
+Other examples of Interactions where feedback is important include direct manipulation. This is triggering actions by dragging icons on targets to trigger actions (drag the document on the trash can will delete it) or moving object handles to change the objects size or appearance.
 Not offering feedback will confuse and frustrate users - immediate and well designed feedback will make them feel good as they feel in control of the system.