36
edits
No edit summary |
|||
(3 intermediate revisions by one other user not shown) | |||
Line 48: | Line 48: | ||
[add User] | [add User] | ||
#1 The explanation of the dialog says you should enter the email address of the person you would add. This could | #1 The explanation of the dialog says you should enter the email address of the person you would add. This could maybe confusing because people could think they could add all people with an email address. | ||
#2 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. | #2 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. | ||
== Recognition rather than recall == | == Recognition rather than recall == | ||
Line 67: | Line 64: | ||
All dialogs and messages I have seen inside ChatSecure did exactly that they where designed for. There where some little problems with the description of the dialog but this are fine details. Extra information and settings, which the basic user does not need, are accessable via an extra menu. I am not that familiar with the Android Design Guidelines, but for me looked like it should on android. Also the interface is reduced to the minimal necessary elements which is also helpful for the user. | All dialogs and messages I have seen inside ChatSecure did exactly that they where designed for. There where some little problems with the description of the dialog but this are fine details. Extra information and settings, which the basic user does not need, are accessable via an extra menu. I am not that familiar with the Android Design Guidelines, but for me looked like it should on android. Also the interface is reduced to the minimal necessary elements which is also helpful for the user. | ||
<!-- "...did exactly what..." "for me it looked" "is also reduced" | |||
== Help users recognize, diagnose and recover from errors == | == Help users recognize, diagnose and recover from errors == | ||
For now I have not seen some error messages, but from former versions i remember some. There where all very technical and not saying. 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. | For now I have not seen some error messages, but from former versions i remember some. There where all very technical and not saying. 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. | ||
<!-- "They were...." "deal with them" "a detail button" | |||
== Help and documentation == | == Help and documentation == | ||
A detailed or even basic help is missing for now. In my opinion 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. | A detailed or even basic help is missing for now. In my opinion 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. | ||
<!-- "be nice"--> | |||
== Bugs == | == Bugs == | ||
Line 88: | Line 91: | ||
* [chat window] | * [chat window] | ||
Chat partner is shown as offline even if he is online. | Chat partner is shown as offline even if he is online. | ||
<!-- Würde ich ales zu "consistency and standard" stecken. --> |
edits