IFD:Nutzerstudien WiSe1314/Gruppe Anmeldung endpresentation - Revision history

Lisa.guth: /* Observation */

2014-03-19T10:23:18Z

Observation

← Older revision		Revision as of 10:23, 19 March 2014
Line 118:		Line 118:

	What is noticeable during that usability test?		What is noticeable during that usability test?
	* first part: login with an existing account (all input data are given)		* first part of the video: login with an existing account (all input data are given)
	input of		input of
	# user domain		# user domain
Line 127:		Line 127:


	* second part: to explore the app by yourself		* second part of the video: to explore the app by yourself

	Now in the second part of the usability test the user should explore the app ChatSecure by herself and think loud while testing and exploring. So it was easy to analyse all the steps she made in the test but was not distracted by questions or other confounding factors.		Now in the second part of the usability test the user should explore the app ChatSecure by herself and think loud while testing and exploring. So it was easy to analyse all the steps she made in the test but was not distracted by questions or other confounding factors.

Lisa.guth: /* Observation */

2014-03-19T10:22:09Z

Observation

← Older revision		Revision as of 10:22, 19 March 2014
Line 117:		Line 117:


	* What is noticeable during that usability test?		What is noticeable during that usability test?
			* first part: login with an existing account (all input data are given)
			input of
			# user domain
			# password
			# put check mark without any hint
			# log on
			So in the first part the login process with an existing account works very good and the given task was solved


			* second part: to explore the app by yourself

			Now in the second part of the usability test the user should explore the app ChatSecure by herself and think loud while testing and exploring. So it was easy to analyse all the steps she made in the test but was not distracted by questions or other confounding factors.
			# online status of the contacts were unclear
			# ciphering and how it works in the app was not clear. By trial and error the user understands the mechanism with the open and close lock and the color symbolism.
			# OTR: in the beginning the user don't know what to do with OTR. It was the same process as 2)
			# verifying fingerprint: there are given three opportunities but there is no explanation what is the result or for what it is useful.

			So the second part was very revealing because the user had no given task, she only should explore an try out the app by herself. You can see the unaffected way of proceeding of the user and the occuring problems.

	During the test we found out...		During the test we found out...

Lisa.guth: /* Observation */

2014-03-18T14:28:33Z

Observation

← Older revision		Revision as of 14:28, 18 March 2014
Line 111:		Line 111:
	With that method and the video it was possible to find and analyse the issues the tester had.		With that method and the video it was possible to find and analyse the issues the tester had.

	[https://www.youtube.com/watch?v=~~zdeTEaDdvy4~~&feature=youtu.be Usability test]		[https://www.youtube.com/watch?v=TwxaKDFEOmY&feature=youtu.be Usability test\| bessere Qualität]
	<br><br><br>		<br><br><br>

Lisa.guth: /* First design considerations and ideas */

2014-03-18T13:01:06Z

First design considerations and ideas

← Older revision		Revision as of 13:01, 18 March 2014
Line 224:		Line 224:

	1. We want the process of creating an account and signing in as intuitive as possible (comparable with WhatsApp and Facebook Messenger)		1. We want the process of creating an account and signing in as intuitive as possible (comparable with WhatsApp and Facebook Messenger)
			<br>
	2. We want the app as safe as possible (safer than WhatsApp and Facebook Messenger)		2. We want the app as safe as possible (safer than WhatsApp and Facebook Messenger)

Line 232:		Line 233:

	<span style="color:#ee9966">One thing to consider with the password is whether it is a good idea for the app to not remember the password. Certain high-risk users might want to avoid saving their password on the phone in case the phone is lost. But if the password is stored in a way that it cannot be recovered, and access to the app requires a password on a lock screen, then there is no longer a good reason to avoid saving the password. ChatSecure can now do both: it stores everything encrypted, and it has a lock screen for the whole app. In this case, I think it makes sense to remove the option for saving the account password, and just make it always save it. Then perhaps ChatSecure can forget the password if the user forces a logout. I believe this is how the Facebook app handles the password: it automatically remembers it until the user manually requests to logout.</span>		<span style="color:#ee9966">One thing to consider with the password is whether it is a good idea for the app to not remember the password. Certain high-risk users might want to avoid saving their password on the phone in case the phone is lost. But if the password is stored in a way that it cannot be recovered, and access to the app requires a password on a lock screen, then there is no longer a good reason to avoid saving the password. ChatSecure can now do both: it stores everything encrypted, and it has a lock screen for the whole app. In this case, I think it makes sense to remove the option for saving the account password, and just make it always save it. Then perhaps ChatSecure can forget the password if the user forces a logout. I believe this is how the Facebook app handles the password: it automatically remembers it until the user manually requests to logout.</span>



	==Prototypes==		==Prototypes==

Lisa.guth: /* Prototypes */

2014-03-18T12:14:47Z

Prototypes

← Older revision		Revision as of 12:14, 18 March 2014
Line 280:		Line 280:
	At this juncture we considered that it is very important that the user could follow all of his actions and understands the results.		At this juncture we considered that it is very important that the user could follow all of his actions and understands the results.
	We also wanted a clear and visible design to show the system status.		We also wanted a clear and visible design to show the system status.
	<br>We added info buttons near interface-Elements that were misunderstood in our tests. So the user can get fast help without ~~serching~~ for it very long. We think this is a solution helping new users and not annoying user with a bigger knowledge. (images 5,6,7)		So we went trough the first steps an change some details so that all steps are clear for the user.
			<br>We added info buttons near interface-Elements that were misunderstood in our tests. So the user can get fast help without searching for it very long. We think this is a solution helping new users and not annoying user with a bigger knowledge. (images 5,6,7)


	<span style="color:#ee9966">The idea of allowing people to find out more info on the account setup screen is quite valuable. One thing to also consider is how to use information that the program can automatically detect. For example, Tor/Orbot is a separate app, and ChatSecure can detect if it is installed or not. So ChatSecure could change the account setup screen based on that.</span>		<span style="color:#ee9966">The idea of allowing people to find out more info on the account setup screen is quite valuable. One thing to also consider is how to use information that the program can automatically detect. For example, Tor/Orbot is a separate app, and ChatSecure can detect if it is installed or not. So ChatSecure could change the account setup screen based on that.</span>

			For all ordinary citizen it's not clear what is meant with Tor/Orbot respectively they don't know that it is a separate app. So it would useful to give a hint in an infomation window about this topic and allows the user to decide between diffenrent procedures to go on.

			In the last two picture (image 9 and 10) you see the screen, in which the user can quickly switch between several accounts.


Line 298:		Line 303:

	<br>Furthermore we improved the design for the list of contacts once more and clearly seperated "online" and "offline" from each other in order to prevent mistakes and confusion. This two lists are know reachable with a kind of "tabs". (images 11, 13,14)		<br>Furthermore we improved the design for the list of contacts once more and clearly seperated "online" and "offline" from each other in order to prevent mistakes and confusion. This two lists are know reachable with a kind of "tabs". (images 11, 13,14)
			In the first two pictures there is our "old" design with the two lists marked with the corresponding colors . The light blue bar at the left side points to an unread message.
			Our new idea of separating the two lists was implement with tabs (image 13 and 14). You can clearly see in which tab you are because this one in colored and the other one is grayed out.
	<br>		<br>
	<span style="color:#598193">Bezug zu Bildern herstellen (wie in der Mail angemerkt)</span>		<span style="color:#598193">Bezug zu Bildern herstellen (wie in der Mail angemerkt)</span>

Lisa.guth: /* Prototypes */

2014-03-18T11:40:31Z

Prototypes

← Older revision		Revision as of 11:40, 18 March 2014
Line 252:		Line 252:
	[[File:nutzerstudien_version1_1.JPG\|200px\| additional password entering button]]		[[File:nutzerstudien_version1_1.JPG\|200px\| additional password entering button]]
	[[File:nutzerstudien_version1_2.JPG\|200px\| your own status, so you can choose between different status types]]		[[File:nutzerstudien_version1_2.JPG\|200px\| your own status, so you can choose between different status types]]
			<br>
	<br>		<br>
	<br>		<br>
	'''Version 2'''		'''Version 2'''
			<br>

	<br>		<br>
	Our next steps for our prototypes were to thought about a clear arrangement of the contact online/contact offline menu.		Our next steps for our prototypes were to thought about a clear arrangement of the contact online/contact offline menu.
	In our usability tests we found out, that the design is very confusing and the tester couldn't really find out wich contact was online and who not.		In our usability tests we found out, that the design is very confusing and the tester couldn't really find out wich contact was online and who not.
	<br>Moreover we separated the symbol of the own status and the symbol of the contact's status, so there's no more confusion.		So in the first two pictures and in the last one you can see different ways of representation of the contact menu. At the top you see online/offline and at the left side you see accessorily the color symbolism green/red. In the first one there is an extra area (yellow) for these contact, which are "beschäftigt".
			<br>Moreover we separated the symbol of the own status and the symbol of the contact's status, so there's no more confusion. Now you can change your status by clicking on the lock and it will change the color according to your status (image 3).
	Now it's clear what your own status is and what's the status of your contacts.		Now it's clear what your own status is and what's the status of your contacts.
	<br>We also added a yellow star on the right side next to the contact's name. That's optional for every contact and a way to fix your favourite contacts on top of the list.		<br>We also added a yellow star on the right side next to the contact's name. That's optional for every contact and a way to fix your favourite contacts on top of the list.
			<br>

	<br>		<br>
	[[File:nutzerstudien_version2_1.JPG\|200px]]		[[File:nutzerstudien_version2_1.JPG\|200px]]
Line 271:		Line 271:
	[[File:nutzerstudien_version2_4.JPG\|200px]]		[[File:nutzerstudien_version2_4.JPG\|200px]]
	[[File:nutzerstudien_version2_5.JPG\|200px]]		[[File:nutzerstudien_version2_5.JPG\|200px]]
			<br>
	<br>		<br>
	<br>		<br>
	'''Version 3'''		'''Version 3'''
			<br>
	<br>		<br>
	For the next iteration we focused on improving the progress of creating an account.		For the next iteration we focused on improving the progress of creating an account.

Lisa.guth: /* Prototypes */

2014-03-18T11:21:17Z

Prototypes

← Older revision		Revision as of 11:21, 18 March 2014
Line 248:		Line 248:


	[[File:Prototyp Anmeldeprozess.jpg\|600px]]		[[File:Prototyp Anmeldeprozess.jpg\|600px\| Overview of our first paper prototype]]
	<br>		<br>
	[[File:nutzerstudien_version1_1.JPG\|200px]]		[[File:nutzerstudien_version1_1.JPG\|200px\| additional password entering button]]
	[[File:nutzerstudien_version1_2.JPG\|200px]]		[[File:nutzerstudien_version1_2.JPG\|200px\| your own status, so you can choose between different status types]]
	<br>		<br>
	<br>		<br>

SusanneP: /* Observation */

2014-03-14T21:33:48Z

Observation

← Older revision		Revision as of 21:33, 14 March 2014
Line 127:		Line 127:
	Results:		Results:
	We evaluated the usability tests and made a heuristic analysis for creating a new account and the login-progress.		We evaluated the usability tests and made a heuristic analysis for creating a new account and the login-progress.
	<span style="color:#598193">Der Abschnitt zu Observation zeigt eine gute Strukturierung, da bin ich sehr gespannt auf die Ergebnisse dieser Tests. leider steht unter "What is noticeable during that usability test?" nur welcher Art die Ergebnisse sind ("which problems appeared") und nicht was die Ergebnisse selber sind ("Problems: The ''foo'' irritates users, because it looks like the ''bar'' they already know from ''qux'') Auch die Heuristische Analyse, die ihr gemacht habt, hat eine kurze Hinleitung und deutliche Erwähnung verdient!</span>

			<span style="color:#598193">Der Abschnitt zu Observation zeigt eine gute Strukturierung, da bin ich sehr gespannt auf die Ergebnisse dieser Tests. leider steht unter "What is noticeable during that usability test?" nur welcher Art die Ergebnisse sind ("which problems appeared") und nicht was die Ergebnisse selber sind ("Problems: The ''foo'' irritates users, because it looks like the ''bar'' they already know from ''qux'')</span>

			In the course of our course we learned about the 10 most general principles for interaction design. To understand this so called "heuristics" and to get in touch with them we did an analysis with the app. This is what we found out:
	[http://www.uni-weimar.de/medien/wiki/IFD:Nutzerstudien_WiSe1314/HeuristicAnalysisAnmeldung heuristic analysis]		[http://www.uni-weimar.de/medien/wiki/IFD:Nutzerstudien_WiSe1314/HeuristicAnalysisAnmeldung heuristic analysis]

	<span style="color:#ee9966">The heuristic analysis provides a thorough overview of the issues discovered in the user testing. It would be interesting to see links to specific quotes and actions of users in the testing in relation to the points in the analysis. Then if I want to understand a specific problem better, I find the quotes, or reference in the video (you can link to specific times in a youtube video, for example).</span>		<span style="color:#ee9966">The heuristic analysis provides a thorough overview of the issues discovered in the user testing. It would be interesting to see links to specific quotes and actions of users in the testing in relation to the points in the analysis. Then if I want to understand a specific problem better, I find the quotes, or reference in the video (you can link to specific times in a youtube video, for example).</span>


	=='''Data Analysis & Main Results'''==		=='''Data Analysis & Main Results'''==

SusanneP: /* Data gathering: Interviews */

2014-03-14T21:25:19Z

Data gathering: Interviews

← Older revision		Revision as of 21:25, 14 March 2014
Line 79:		Line 79:

	<span style="color:#ee9966">In person interviews can give you a lot of focused time and information, and can be quite valuable. Did you consider any other less focused methods of gathering information? Like a survey via facebook, etc. Having a more neutral method of getting information from people might give you things that would not be mentioned in an interview.</span>		<span style="color:#ee9966">In person interviews can give you a lot of focused time and information, and can be quite valuable. Did you consider any other less focused methods of gathering information? Like a survey via facebook, etc. Having a more neutral method of getting information from people might give you things that would not be mentioned in an interview.</span>

			Unfortunately we don't made any surveys e.g. on facebook. But that's a very interesting idea and we sure will use these methods next time.

	Central questions:		Central questions:
Line 95:		Line 97:
	<span style="color:#ee9966">This is a good range of questions that sounds likely to bring out some of the harder issues of the interface, like finding the threshold where people will give up some security because the interface is too difficult to use. Like the comment above, some of the questions might be too vague without follow-up information. Perhaps there needs to be a couple more targeted questions about examples of when the user gave up on security because of usability issues.</span>		<span style="color:#ee9966">This is a good range of questions that sounds likely to bring out some of the harder issues of the interface, like finding the threshold where people will give up some security because the interface is too difficult to use. Like the comment above, some of the questions might be too vague without follow-up information. Perhaps there needs to be a couple more targeted questions about examples of when the user gave up on security because of usability issues.</span>

			Thank you! We'll try it next time.

	==Observation==		==Observation==

Hans at 18:37, 14 March 2014

2014-03-14T18:37:44Z

← Older revision		Revision as of 18:37, 14 March 2014
Line 326:		Line 326:
	<span style="color:#598193">Überblick am Schluss: Sehr gut. Wie in der Mail angemerkt, wäre hier ein guter Platz für eine Zusammenfassung der Änderungen, sozusagen ein Design-Fazit.</span>		<span style="color:#598193">Überblick am Schluss: Sehr gut. Wie in der Mail angemerkt, wäre hier ein guter Platz für eine Zusammenfassung der Änderungen, sozusagen ein Design-Fazit.</span>

	FINAL DESIGN RESULTS/UPDATES FOR CHATSECURE:		FINAL DESIGN RESULTS/UPDATES FOR CHATSECURE:

	<span style="color:#ee9966">This is a much clearer representation of the password prompt than what currently exists.</span>		<span style="color:#ee9966">This is a much clearer representation of the password prompt than what currently exists.</span>