36
edits
IFD:Nutzerstudien WiSe1314/HeuristicAnalysisSecurity (view source)
Revision as of 14:00, 23 January 2014
, 23 January 2014no edit summary
No edit summary |
|||
| Line 39: | Line 39: | ||
* The touch screen doesn`t work sometimes, when clicking on “Add a contact”. | * The touch screen doesn`t work sometimes, when clicking on “Add a contact”. | ||
* Most elements inside ChatSecure are clickable. For example the status button or the current status message. The name of the chat partner is underlined. For the first time I have thought it is clickable and tried it. This means I expected a reaction on my click, like the other interface elements would do. Later a figured out that this marks the current chat-tab. | |||
* If you open up the context menu you will see an exit button at the bottom. In my opinion this should not be there. Instead this functionality should be provided by the home button. | |||
* The settings menu is hidden behind the three points. Today most mobile device users expect some kind of gear-wheel or screw-wrench. Maybe it would be better to change the three points into something like that. If the three points are a place-holder for an collection of options it should be more clear what is meant with this symbol. | |||
== Error prevention == | == Error prevention == | ||
| Line 49: | Line 55: | ||
[[File:Screenshot_2014-01-09-11-16-06.png]] | [[File:Screenshot_2014-01-09-11-16-06.png]] | ||
* The explanation of the dialog says you should enter the email address of the person you would add. This could my be confusing because people could think they could add all people with an email address. | |||
* If one accidentally touches the area outside the dialog box the process of adding a contact is stopped. The annoying point is that one has to type in the data again if you want to add the contact. | |||
== Recognizing rather than recall == | == Recognizing rather than recall == | ||
| Line 89: | Line 99: | ||
* I have not received any error message from the app. Therefore, no statement about the intelligibility of the message and the quality of the solution paths are taken. | * I have not received any error message from the app. Therefore, no statement about the intelligibility of the message and the quality of the solution paths are taken. | ||
* Error messages very technical and not saying in former versions. Details are fine if one knows how to deal with, but it would be better to give a description of the problem and add an detail Button to see the exact problem. | |||
== Help and dokumentation == | == Help and dokumentation == | ||
* A help is not available in the menu. This would be very helpful for "beginners". E.g. the traffic light system for the security of the message isn’t immediately clear. | * A help is not available in the menu. This would be very helpful for "beginners". E.g. the traffic light system for the security of the message isn’t immediately clear. It would be nice to have a short tutorial explaining the background for the user. This should easily explain what is OTR, what is a fingerprint and maybe some reasons why one should use the encryption. It could also ne nice to have a short Q/A part where some basic questions like 'Where did i find ...' or 'Is this possible ...' are answered. | ||