IFD:Course Interaction Design: Difference between revisions

IFD:Course Interaction Design (view source)

Revision as of 13:39, 3 October 2010

44 bytes removed , 3 October 2010

→‎Savety

JanD

Bureaucrats, emailconfirmed

1,221

edits

@@ Line 53: / Line 53: @@
 ====Savety====
 Savety is protecting the user and his/her creations from undesired outcomes. Very basic is that you provide a product that does not crash and destroys the users data by doing so.
-You should as well prevent that the user selects data-destroing functions by accident. E.g. putting the "save" and the "close" entry close to each other in a menu will cause data loss: if the user wants to save, he may press "no" after a dialog window appears: "don't bother me now. I want to save my data! What was this dialog window anyway? oooohhhh shit!" - the data is lost, "close" was selected by accident and the dialog window that was dismissed by choosing "no" was the final warning.
+You should as well prevent that the user selects data-destroying functions by accident. E.g. putting the "save" and the "close" entry close to each other in a menu will cause data loss: if the user wants to save, he may press "no" after a dialog window appears: "don't bother me now. I want to save my data!" - and the data is lost, "close" was selected by accident and the dialog window that was dismissed by choosing "no" was the final warning.
 Even if you prevent accidental actions the users data is not save. Users may misunderstand the name of an action or just try out what the result will look like. Therefore you should provide an undo-facility. This means the user can do an action and if it turns out that this has been a bad idea it can be undone. This is a great feature that demands a bit of thinking when the code is written but it is worth it. As a side effect your application becomes more learnable as well: users are able to learn by doing without any worries.