53
edits
IFD:Nutzerstudien WiSe1314/Gruppe Anmeldung endpresentation (view source)
Revision as of 15:04, 30 January 2014
, 30 January 2014no edit summary
No edit summary |
No edit summary |
||
| Line 15: | Line 15: | ||
'''2. Analyse and Assessment''' | '''2. Analyse and Assessment''' | ||
After that we analysed the results (infinity diagramming) by summing up, comparing and strucuring. | After that we analysed the results (infinity diagramming) by summing up, comparing and strucuring them. | ||
'''3. Prototypes and scenarios''' | '''3. Prototypes and scenarios''' | ||
| Line 26: | Line 26: | ||
=='''Data gathering: Interviews | =='''Data gathering: Interviews'''== | ||
interview partner: | table of interview partner: | ||
{| class="wikitable" | {| class="wikitable" | ||
| Line 86: | Line 86: | ||
==Observation== | ==Observation== | ||
* What observations during the interviews did we make? | |||
--> here the video can be integrated! | |||
what is noticeable during these usability test? | |||
(After that we did some usability tests of the app (ChatSecure) to find out how others deal with the login process. We wanted to find out if the register and login process is intuitive for the user or not. So we got to know about user's handling with apps and their expectations. We hoped to get suggestions and ideas for a better log in process based on the user's behavior.) | |||
| Line 134: | Line 141: | ||
'''Plans – how we want to solve the problem(s)''' | '''Plans – how we want to solve the problem(s)''' | ||
Method 1: Other application's test | * Method 1: Other application's test | ||
First we start to analyse the login process at other applications. | First we start to analyse the login process at other applications. | ||
| Line 151: | Line 158: | ||
Both applications manage without a password. That's quite intuitive but it isn't quite save. While doing our interviews we experienced that it would be convenient to have a password to have a safety warranty (e.g. in case of losing the smartphone) | Both applications manage without a password. That's quite intuitive but it isn't quite save. While doing our interviews we experienced that it would be convenient to have a password to have a safety warranty (e.g. in case of losing the smartphone) | ||
We want | ==First design considerations and ideas== | ||
We want ChatSecure as intuitive as WhatsApp and Facebook Messenger but we also want it to be staying save. So there have to be an additional button for entering a password and we want to reduce redundant buttons and clarify inconclusive and obscure functions/buttons. | |||
==Prototypes== | ==Prototypes== | ||
| Line 170: | Line 176: | ||
==Our conclusions== | ==Our conclusions== | ||
problems we had | * problems we had | ||
what we would do better next time | * what we would do better next time | ||
our final design | * our final design | ||