IFD:Nutzerstudien WiSe1314/Gruppe Anmeldung endpresentation: Difference between revisions

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

Central questions:

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

==Observation==

With that method and the video it was possible to find and analyse the issues the tester had.

<br><br><br>

During the test we found out...  

Results:

We evaluated the usability tests and made a heuristic analysis for creating a new account and the login-progress.

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

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

** The user likes to express its emotion with a lot of smileys.  

** The function "writes..." is not necessary.  

1. We want the process of creating an account and signing in as intuitive as possible (comparable with WhatsApp and Facebook Messenger)  

2. We want the app as safe as possible (safer than WhatsApp and Facebook Messenger)   

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

'''Version 1'''

<br>

<br>

<br>

'''Version 2'''

<br>

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.  

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>

[[File:nutzerstudien_version2_1.JPG|200px]]

[[File:nutzerstudien_version2_4.JPG|200px]]

[[File:nutzerstudien_version2_5.JPG|200px]]

<br>

<br>

'''Version 3'''

<br>

For the next iteration we focused on improving the progress of creating an account.  

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.  

[[File:nutzerstudien_version3_1.JPG|200px]]

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

<span style="color:#598193">Bezug zu Bildern herstellen (wie in der Mail angemerkt)</span>

[[File:nutzerstudien_version3_11.JPG|200px]]

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

1. additional password entering button  

[[File:nutzerstudien_version4_2.JPG|200px]]

[[File:nutzerstudien_version4_3.JPG|200px]]

4. new contact order with several colours - two different design ideas

[[File:nutzerstudien_version3_11.JPG|200px]]

[[File:nutzerstudien_version3_13.JPG|200px]]

5. yellow stars for most important contacts  

[[File:nutzerstudien_version3_11.JPG|200px]]

6. info buttons to improve the user understanding

[[File:nutzerstudien_version3_4.JPG|200px]]

The first user experiences by ourselves with the app "ChatSecure" passed dragging because of difficulties with the process of creating an account. We lost too much time by trying to test the app. It was a huge problem that the app didn't worked with IOS.   

   

Furthermore we were well prepared before interviewing so that we could implement that while talking to our target group.