IFD:Nutzerstudien WiSe1314/Gruppe Anmeldung - Revision history

Kede7290 at 14:15, 30 January 2014

2014-01-30T14:15:45Z

← Older revision		Revision as of 14:15, 30 January 2014
Line 8:		Line 8:
	For that purpose we tested the app "ChatSecure" and tried to improve the design based on usability tests.		For that purpose we tested the app "ChatSecure" and tried to improve the design based on usability tests.

	Our main focus premised on the process of creating an account and of signing in.		Our main focus premised on the process of creating an account and of signing in. Our general process was:

	'''Interviews and target group'''		'''Interviews and target group'''

Kede7290 at 14:06, 30 January 2014

2014-01-30T14:06:20Z

← Older revision		Revision as of 14:06, 30 January 2014
Line 1:		Line 1:
	'''~~[[Documentation]]~~'''		'''DOCUMENTATION'''


	'''Course Aims'''		'''Course Aims'''
Line 8:		Line 9:

	Our main focus premised on the process of creating an account and of signing in.		Our main focus premised on the process of creating an account and of signing in.
	For that reason we started to interview a few people from our social environment. After that we analysed the results (infinity diagramming) and began to create prototypes. These prototypes also passed through usability tests to further improve the design.
	For that prototypes we constructed scenarios which had to be accomplished by the test users. ~~So we~~ further improved our design by iteration to get our final design.		'''Interviews and target group'''
			For that reason we started to interview a few people from our social environment as our target group. So we focused on students at the age of 20 - 30. We reached this test persons personally so we met them to conduct the interviews directly.

			'''Analyse and Assessment'''
			After that we analysed the results (infinity diagramming) by summing up, comparing and strucuring.

			'''Prototypes and scenarios'''
			Then we began to create prototypes. These prototypes also passed through usability tests to further improve the design.
			For that prototypes we constructed scenarios which had to be accomplished by the test users.

			'''Improving Design by Iteration'''
			We further improved our design by iteration (five steps) to get our final design.


Line 160:		Line 172:

	==Prototypes==		==Prototypes==

			Our first prototype for the login process contains the additional password entering button if it isn't saved. (at the beginning you can choose if you want to save the password for further use or not)
			It occurs when you want to switch from offline to online as an extra field.

	[[File:Prototyp Anmeldeprozess.jpg\|600px]]		[[File:Prototyp Anmeldeprozess.jpg\|600px]]

	~~Our first prototype for the login process contains the additional password entering button.~~


	<div style="color:brown">The difficult part here is that there is no known way of making a secure, private connection without some kind of login process. WhatsApp's uses an automatically generated password that it is not hard for a malicious user to generate, getting full access to the whole account. So its security is very poor, but its usability is great. As far as I know, Facebook does require a login, but it just handles it well and it only happens once really. Facebook is probably a better example here. It probably makes the most sense to compare the Facebook mobile app's first time setup/login procedure with ChatSecure's Facebook login procedure. Then additionally, it would be great to see a comparison of other apps like ChatSecure that allow users to use a wide variety of accounts (Xabber, Beem, etc.) </div>--[[User:Hans\|Hans]] 21:35, 18 December 2013 (CET)		<div style="color:brown">The difficult part here is that there is no known way of making a secure, private connection without some kind of login process. WhatsApp's uses an automatically generated password that it is not hard for a malicious user to generate, getting full access to the whole account. So its security is very poor, but its usability is great. As far as I know, Facebook does require a login, but it just handles it well and it only happens once really. Facebook is probably a better example here. It probably makes the most sense to compare the Facebook mobile app's first time setup/login procedure with ChatSecure's Facebook login procedure. Then additionally, it would be great to see a comparison of other apps like ChatSecure that allow users to use a wide variety of accounts (Xabber, Beem, etc.) </div>--[[User:Hans\|Hans]] 21:35, 18 December 2013 (CET)


			==Our conclusions==
			problems we had
			what we would do better next time
			our final design

Kede7290 at 11:24, 30 January 2014

2014-01-30T11:24:32Z

← Older revision		Revision as of 11:24, 30 January 2014
Line 1:		Line 1:
	[['''Documentation''']]		'''[[Documentation]]'''

	'''Course Aims'''		'''Course Aims'''
Line 8:		Line 8:

	Our main focus premised on the process of creating an account and of signing in.		Our main focus premised on the process of creating an account and of signing in.
	For that reason we started to interview a few people from our social environment. After that we analysed the results (infinity diagramming) and began to create prototypes. These prototypes also passed through usability tests to further improve the design.		For that reason we started to interview a few people from our social environment. After that we analysed the results (infinity diagramming) and began to create prototypes. These prototypes also passed through usability tests to further improve the design.
			For that prototypes we constructed scenarios which had to be accomplished by the test users. So we further improved our design by iteration to get our final design.


Line 118:		Line 119:
	<div style="color:brown">Definitely some interesting results here, it sounds like people are interested in security and are trying to figure out ways to increase their own security. It would be quite valuable to explore ideas of how people represent their concerns, and how they aim to increase their own security. About Authenticity, its a hard concept in computers. I think most computer users don't understand that its easy to fake messages. My guess is that people are concerned about it, but don't really understand the technical issues so they assume things they receive are what they seem to be. A parallel test on this topic could be very illuminating, like showing users how to generate fake emails, messages, etc. to make them appear they are coming from someone they trust. Also, I'm not quite sure what the point of view of all of these bullet points are. Are they from the person running the tests, or are the things that the users in the tests communicated? My guess is that they are all summaries of things communicated from the users.</div>--[[User:Hans\|Hans]] 21:35, 18 December 2013 (CET)		<div style="color:brown">Definitely some interesting results here, it sounds like people are interested in security and are trying to figure out ways to increase their own security. It would be quite valuable to explore ideas of how people represent their concerns, and how they aim to increase their own security. About Authenticity, its a hard concept in computers. I think most computer users don't understand that its easy to fake messages. My guess is that people are concerned about it, but don't really understand the technical issues so they assume things they receive are what they seem to be. A parallel test on this topic could be very illuminating, like showing users how to generate fake emails, messages, etc. to make them appear they are coming from someone they trust. Also, I'm not quite sure what the point of view of all of these bullet points are. Are they from the person running the tests, or are the things that the users in the tests communicated? My guess is that they are all summaries of things communicated from the users.</div>--[[User:Hans\|Hans]] 21:35, 18 December 2013 (CET)

	'''What specific problem we want to solve'''		==First design considerations and ideas==

			'''What specific problem we want to solve'''

	We want to solve some problems with the login-process and make it easier to use.		We want to solve some problems with the login-process and make it easier to use.
Line 156:		Line 159:
	We want it as intuitive as WhatsApp and Facebook Messenger but we also want it to be save. So there have to be an additional button for entering a password.		We want it as intuitive as WhatsApp and Facebook Messenger but we also want it to be save. So there have to be an additional button for entering a password.

			==Prototypes==
	[[File:Prototyp Anmeldeprozess.jpg\|600px]]		[[File:Prototyp Anmeldeprozess.jpg\|600px]]

	Our first prototype for the login process.		Our first prototype for the login process contains the additional password entering button.


	<div style="color:brown">The difficult part here is that there is no known way of making a secure, private connection without some kind of login process. WhatsApp's uses an automatically generated password that it is not hard for a malicious user to generate, getting full access to the whole account. So its security is very poor, but its usability is great. As far as I know, Facebook does require a login, but it just handles it well and it only happens once really. Facebook is probably a better example here. It probably makes the most sense to compare the Facebook mobile app's first time setup/login procedure with ChatSecure's Facebook login procedure. Then additionally, it would be great to see a comparison of other apps like ChatSecure that allow users to use a wide variety of accounts (Xabber, Beem, etc.) </div>--[[User:Hans\|Hans]] 21:35, 18 December 2013 (CET)		<div style="color:brown">The difficult part here is that there is no known way of making a secure, private connection without some kind of login process. WhatsApp's uses an automatically generated password that it is not hard for a malicious user to generate, getting full access to the whole account. So its security is very poor, but its usability is great. As far as I know, Facebook does require a login, but it just handles it well and it only happens once really. Facebook is probably a better example here. It probably makes the most sense to compare the Facebook mobile app's first time setup/login procedure with ChatSecure's Facebook login procedure. Then additionally, it would be great to see a comparison of other apps like ChatSecure that allow users to use a wide variety of accounts (Xabber, Beem, etc.) </div>--[[User:Hans\|Hans]] 21:35, 18 December 2013 (CET)

Kede7290 at 10:36, 30 January 2014

2014-01-30T10:36:54Z

← Older revision		Revision as of 10:36, 30 January 2014
Line 1:		Line 1:
	'''~~Aims of data gathering~~'''		[['''Documentation''']]

			'''Course Aims'''

	During the course "Nutzerstudien" we wanted to know how important security is for students at our age, what they expect from chat apps and what their problems/whishes are. ~~Main~~ focus ~~was also~~ the ~~question~~ of ~~authenticity~~.
	For that reason we started to interview a few people from our social environment.		During the course "Nutzerstudien" we wanted to know how important security is for students at our age, what they expect from chat apps and what their problems/whishes are.
			For that purpose we tested the app "ChatSecure" and tried to improve the design based on usability tests.

			Our main focus premised on the process of creating an account and of signing in.
			For that reason we started to interview a few people from our social environment. After that we analysed the results (infinity diagramming) and began to create prototypes. These prototypes also passed through usability tests to further improve the design.

JanD: moved IFD:Nutzerstudien WiSe1314/Gruppe Authentizität to IFD:Nutzerstudien WiSe1314/Gruppe Anmeldung: Themenwechsel

2013-12-19T14:47:43Z

moved IFD:Nutzerstudien WiSe1314/Gruppe Authentizität to IFD:Nutzerstudien WiSe1314/Gruppe Anmeldung: Themenwechsel

← Older revision	Revision as of 14:47, 19 December 2013
(No difference)

Lisa.guth at 10:51, 19 December 2013

2013-12-19T10:51:18Z

← Older revision		Revision as of 10:51, 19 December 2013
Line 75:		Line 75:

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

			[[File:Nutzerstudien-Authentifizierung.jpg\| 600 px]]

	* App Requirements		* App Requirements

Hans: added my comments

2013-12-18T20:35:16Z

added my comments

← Older revision		Revision as of 20:35, 18 December 2013
Line 89:		Line 89:
	** The user wants to send out photos/videos.		** The user wants to send out photos/videos.
	** The user likes to express its emotion with a lot of smileys.		** The user likes to express its emotion with a lot of smileys.
	** The function "writes..." is not necassary.		** The function "writes..." is not necassary. <div style="color:brown">not quite sure what this is, could you elaborate on it?</div>--[[User:Hans\|Hans]] 21:35, 18 December 2013 (CET)


	* Security		* Security
	** It would be useful to have a password for the app.		** It would be useful to have a password for the app.
	** To feel ~~save~~, the user desires to have a security warranty.		** To feel safe, the user desires to have a security warranty.
	** It is important that apps are immune from viruses.		** It is important that apps are immune from viruses.
	** Important information, link, photos, videos, … are often sent by E-Mail.		** Important information, link, photos, videos, … are often sent by E-Mail.
Line 108:		Line 109:

	<div style="color:blue">I tried to phrase and explain some points in another way. Is it ok? [M.E.]</div>		<div style="color:blue">I tried to phrase and explain some points in another way. Is it ok? [M.E.]</div>
			<div style="color:brown">Definitely some interesting results here, it sounds like people are interested in security and are trying to figure out ways to increase their own security. It would be quite valuable to explore ideas of how people represent their concerns, and how they aim to increase their own security. About Authenticity, its a hard concept in computers. I think most computer users don't understand that its easy to fake messages. My guess is that people are concerned about it, but don't really understand the technical issues so they assume things they receive are what they seem to be. A parallel test on this topic could be very illuminating, like showing users how to generate fake emails, messages, etc. to make them appear they are coming from someone they trust. Also, I'm not quite sure what the point of view of all of these bullet points are. Are they from the person running the tests, or are the things that the users in the tests communicated? My guess is that they are all summaries of things communicated from the users.</div>--[[User:Hans\|Hans]] 21:35, 18 December 2013 (CET)

			'''What specific problem we want to solve'''
	'''What ~~specifc~~ problem we want to solve'''

	We want to solve some problems with the login-process and make it easier to use.		We want to solve some problems with the login-process and make it easier to use.
Line 119:		Line 120:

	<div style="color:blue">We really focus on the sign up process. There is the problem that you don't get an advice to enter the password but it is nessacary. The process is very inconvenient, it needs to many steps till you can start to chat so that we want to create an easier way. [M.E.]</div>		<div style="color:blue">We really focus on the sign up process. There is the problem that you don't get an advice to enter the password but it is nessacary. The process is very inconvenient, it needs to many steps till you can start to chat so that we want to create an easier way. [M.E.]</div>

			<div style="color:brown">I think this is important work since the process is currently confusing, but also complicated so its not easy to fix the usability issues. But its also not such a huge task, so you should be able to get solid results in the time you have in this class.</div>--[[User:Hans\|Hans]] 21:35, 18 December 2013 (CET)


Line 150:		Line 153:

	Our first prototype for the login process.		Our first prototype for the login process.


			<div style="color:brown">The difficult part here is that there is no known way of making a secure, private connection without some kind of login process. WhatsApp's uses an automatically generated password that it is not hard for a malicious user to generate, getting full access to the whole account. So its security is very poor, but its usability is great. As far as I know, Facebook does require a login, but it just handles it well and it only happens once really. Facebook is probably a better example here. It probably makes the most sense to compare the Facebook mobile app's first time setup/login procedure with ChatSecure's Facebook login procedure. Then additionally, it would be great to see a comparison of other apps like ChatSecure that allow users to use a wide variety of accounts (Xabber, Beem, etc.) </div>--[[User:Hans\|Hans]] 21:35, 18 December 2013 (CET)

Hans at 20:18, 18 December 2013

2013-12-18T20:18:31Z

← Older revision		Revision as of 20:18, 18 December 2013
Line 72:		Line 72:
	<div style="color:darkgreen">Great idea. It is not easy though to see why for an outsider. You could fix it by explaining first, why and how you canged to the topic "login" and because of this it could not be part of the interview process one or two weeks ago.</div>--[[User:JanD\|JanD]] 19:58, 13 December 2013 (CET)		<div style="color:darkgreen">Great idea. It is not easy though to see why for an outsider. You could fix it by explaining first, why and how you canged to the topic "login" and because of this it could not be part of the interview process one or two weeks ago.</div>--[[User:JanD\|JanD]] 19:58, 13 December 2013 (CET)
	<div style="color:blue">I tried to explain what we want to achieve with the usability tests. Ok? [M.E.]</div>		<div style="color:blue">I tried to explain what we want to achieve with the usability tests. Ok? [M.E.]</div>
	<div style="color:~~lightgreen~~">I think this is an area that definitely needs analysis from a usability perspective, and having feedback from people who have limited experience with ChatSecure will be quite helpful. Having a few different setup scenarios to test with would be very useful since the login is quite different depending on what kind of account, etc. For example, using the same Google account as the phone should be quite simple. Using a Facebook acocunt should be a little more work, but straightforward. Using any account with Tor/Orbot would be trickier. And perhaps the hardest will be setting up an account on a server like jabber.ccc.de</div>--[[User:Hans\|Hans]] 21:17, 18 December 2013 (CET)		<div style="color:brown">I think this is an area that definitely needs analysis from a usability perspective, and having feedback from people who have limited experience with ChatSecure will be quite helpful. Having a few different setup scenarios to test with would be very useful since the login is quite different depending on what kind of account, etc. For example, using the same Google account as the phone should be quite simple. Using a Facebook acocunt should be a little more work, but straightforward. Using any account with Tor/Orbot would be trickier. And perhaps the hardest will be setting up an account on a server like jabber.ccc.de</div>--[[User:Hans\|Hans]] 21:17, 18 December 2013 (CET)

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

Hans: comment on question

2013-12-18T20:17:49Z

comment on question

← Older revision		Revision as of 20:17, 18 December 2013
Line 72:		Line 72:
	<div style="color:darkgreen">Great idea. It is not easy though to see why for an outsider. You could fix it by explaining first, why and how you canged to the topic "login" and because of this it could not be part of the interview process one or two weeks ago.</div>--[[User:JanD\|JanD]] 19:58, 13 December 2013 (CET)		<div style="color:darkgreen">Great idea. It is not easy though to see why for an outsider. You could fix it by explaining first, why and how you canged to the topic "login" and because of this it could not be part of the interview process one or two weeks ago.</div>--[[User:JanD\|JanD]] 19:58, 13 December 2013 (CET)
	<div style="color:blue">I tried to explain what we want to achieve with the usability tests. Ok? [M.E.]</div>		<div style="color:blue">I tried to explain what we want to achieve with the usability tests. Ok? [M.E.]</div>
			<div style="color:lightgreen">I think this is an area that definitely needs analysis from a usability perspective, and having feedback from people who have limited experience with ChatSecure will be quite helpful. Having a few different setup scenarios to test with would be very useful since the login is quite different depending on what kind of account, etc. For example, using the same Google account as the phone should be quite simple. Using a Facebook acocunt should be a little more work, but straightforward. Using any account with Tor/Orbot would be trickier. And perhaps the hardest will be setting up an account on a server like jabber.ccc.de</div>--[[User:Hans\|Hans]] 21:17, 18 December 2013 (CET)

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

Kede7290 at 21:20, 17 December 2013

2013-12-17T21:20:44Z

← Older revision		Revision as of 21:20, 17 December 2013
Line 130:		Line 130:

	1. WhatsApp		1. WhatsApp

	This application doesn't contain a login process. You only have to choose the app to be online and you directly see all of your conversations. It is quite easy and intuitive.		This application doesn't contain a login process. You only have to choose the app to be online and you directly see all of your conversations. It is quite easy and intuitive.

	2. Facebook Messenger		2. Facebook Messenger

	This application functions nearly the same way as WhatsApp, so you don't need a password to sign in.		This application functions nearly the same way as WhatsApp, so you don't need a password to sign in.