IFD:Nutzerstudien WiSe1314/HeuristicAnalysisSecurity Person6 - Revision history

Nioerd at 14:00, 23 January 2014

2014-01-23T14:00:19Z

← Older revision		Revision as of 14:00, 23 January 2014
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 ~~my be~~ confusing because people could think they could add all people with an email address.		#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.


	~~<!-- Das "my" ist wahrscheinlich nur aus Versehen noch da. Ansonsten, wunderbar. -->~~

	== Recognition rather than recall ==		== Recognition rather than recall ==

Xicu1652: /* Bugs */

2014-01-23T13:27:13Z

Bugs

← Older revision		Revision as of 13:27, 23 January 2014
Line 94:		Line 94:
	* [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. -->

Xicu1652 at 13:24, 23 January 2014

2014-01-23T13:24:44Z

← Older revision		Revision as of 13:24, 23 January 2014
Line 73:		Line 73:

	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 ==

Xicu1652: /* Aesthetic and minimal design */

2014-01-23T13:20:03Z

Aesthetic and minimal design

← Older revision		Revision as of 13:20, 23 January 2014
Line 67:		Line 67:

	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 ==

Xicu1652: /* Recognition rather than recall */

2014-01-23T13:13:15Z

Recognition rather than recall

← Older revision		Revision as of 13:13, 23 January 2014
Line 57:		Line 57:

	The most complex part of ChatSecure is the setup process. But the user is well guided through. There is no need to remember things from former steps. Possible options are accessable through the settings menu. Features could there be turned on an off which is what a user expects.		The most complex part of ChatSecure is the setup process. But the user is well guided through. There is no need to remember things from former steps. Possible options are accessable through the settings menu. Features could there be turned on an off which is what a user expects.

			<!-- "There features could be turned on an off, which is what a user expects."-->

	== Flexibility and efficiency of use ==		== Flexibility and efficiency of use ==

Xicu1652: /* Error prevention */

2014-01-23T13:10:21Z

Error prevention

← Older revision		Revision as of 13:10, 23 January 2014
Line 50:		Line 50:
	#1 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.		#1 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.
	#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.


			<!-- Das "my" ist wahrscheinlich nur aus Versehen noch da. Ansonsten, wunderbar. -->

	== Recognition rather than recall ==		== Recognition rather than recall ==

Xicu1652: /* Consistency and standards */

2014-01-23T13:04:01Z

Consistency and standards

← Older revision		Revision as of 13:04, 23 January 2014
Line 37:		Line 37:
	# 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.		# 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.		# 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.


			<!-- # "This means" klingt unschön und ich weiß nicht, ob es das in eng. gibt, "so" sagt dasselbe. Was meinst du mit "marks", dass das ganze Chat-Fenster markiert im Sinne von "ausgewählt" worden ist?

			# Bitte Screenshot. Und was ist genau das Kontextmenü? Die "home"-Seite dann?

			# Einwandfrei. Passt auch alles in die Kategorie.-->

	== Error prevention ==		== Error prevention ==

Xicu1652: /* User control and freedom */

2014-01-23T12:57:02Z

User control and freedom

← Older revision		Revision as of 12:57, 23 January 2014
Line 29:		Line 29:

	In my opinion there is no need for a undo / redo functionality in that kind of application. Everything is accessable and one could return to the former step / place by using the device return button.		In my opinion there is no need for a undo / redo functionality in that kind of application. Everything is accessable and one could return to the former step / place by using the device return button.

			<!-- Wieder das "accessable". Das Wort device würde ich streichen. Ansonsten einwandfrei. -->

	== Consistency and standards ==		== Consistency and standards ==

Xicu1652: /* Match between system and the real world */

2014-01-23T12:54:11Z

Match between system and the real world

← Older revision		Revision as of 12:54, 23 January 2014
Line 23:		Line 23:

	The interface 'speaks' the users language. This means today most people try using chat secure are familiar with that kind of application. ChatSecure doesn't make an exception, so it should be easy accessable.		The interface 'speaks' the users language. This means today most people try using chat secure are familiar with that kind of application. ChatSecure doesn't make an exception, so it should be easy accessable.

			<!-- "So today most people trying to use chat secure are familiar with that kind of application." - Accessable? Understandable wäre vielleicht besser, da ich gerade gedacht habe, dass du meinst, dass viele "Zugang" im Sinne von "Zugriff" darauf haben. Ist ja so nicht wahr, da praktisch nur Android-Nutzer Zugriff darauf haben. -->

	== User control and freedom ==		== User control and freedom ==

Xicu1652: /* Visibility of system status */

2014-01-23T12:48:46Z

Visibility of system status

← Older revision		Revision as of 12:48, 23 January 2014
Line 16:		Line 16:

	=>OTR does not work at all.		=>OTR does not work at all.


			<!-- Alles gut, den Punkt hab ich auch, auch in derselben Kategorie. Nur dass sich bei mir nicht mal ein Kreis dreht, der den Status anzeigt. -->

	== Match between system and the real world ==		== Match between system and the real world ==