Bureaucrats, emailconfirmed
1,221
edits
IFD:Nutzerstudien WiSe1314/Gruppe Anmeldung endpresentation (view source)
Revision as of 15:35, 8 March 2014
, 8 March 2014no edit summary
No edit summary |
|||
| Line 5: | Line 5: | ||
We wanted to find out about the importance of security in chat apps for students at our age. Further we were interessted in generelly expectations they have from chat apps and what their problems/whishes are. | We wanted to find out about the importance of security in chat apps for students at our age. Further we were interessted in generelly expectations they have from chat apps and what their problems/whishes are. | ||
For that purpose we tested the app "ChatSecure" with our target group, accomplished usability tests and so developed a varied design to improve the process of creating an account and of signing in. | For that purpose we tested the app "ChatSecure" with our target group, accomplished usability tests and so developed a varied design to improve the process of creating an account and of signing in. | ||
| Line 14: | Line 15: | ||
'''2. Analyse and Assessment''' | '''2. Analyse and Assessment''' | ||
After that we analysed the results (infinity diagramming) by summing up, comparing and strucuring them. | After that we analysed the results (infinity diagramming) by summing up, comparing and strucuring them. | ||
<span style="color:#598193"> Die Analyse macht sehr viel Arbeit. Leider wurde die Methode nicht infinity-diagramming genannt, obwohl das durchaus treffend wäre :-) </span> | |||
'''3. Prototypes and scenarios''' | '''3. Prototypes and scenarios''' | ||
| Line 22: | Line 24: | ||
We further improved our design by iteration (five steps) to get our final design. | We further improved our design by iteration (five steps) to get our final design. | ||
<span style="color:#598193">Ich denke, dass ''Progress of work'' und ''Course aims'' eine gute und einfache Einleitung sind. </span> | |||
=='''Data gathering: Interviews'''== | =='''Data gathering: Interviews'''== | ||
| Line 66: | Line 68: | ||
We wanted to figure out the differences between the students of Arts, Fine Arts/Design and Science/Engineering. So we chose people from our social environment. Because we are students from different courses of studies (Arts, Fine Arts/Design and Science/Engineering) we had the chance to interview these types of students. Thereby we had a huge spectrum of users. | We wanted to figure out the differences between the students of Arts, Fine Arts/Design and Science/Engineering. So we chose people from our social environment. Because we are students from different courses of studies (Arts, Fine Arts/Design and Science/Engineering) we had the chance to interview these types of students. Thereby we had a huge spectrum of users. | ||
<span style="color:#598193">Ich habt Menschen aus der selben Gruppe wie ihr ausgewählt (Studierende ähnlicher Fächer). Vielleicht klingt "huge spectrum" dann etwas übertrieben.</span> | |||
Form of accessibility: | Form of accessibility: | ||
| Line 83: | Line 86: | ||
* What measures do you probably adopt to be safe? | * What measures do you probably adopt to be safe? | ||
* What functions and design features do you find most important for a chat app? | * What functions and design features do you find most important for a chat app? | ||
<span style="color:#598193">''Kleine Anmerkung für zukünftige Projekte: Fragen "what are the requirements…" und "how often…" sind schwierig gut zu beantworten und ihr erfahrt dadurch vermutlich wenig über die Gründe für das Nutzerverhalten. "Advantages… Disadvantages" und "which measures" sind gut. Fragt nicht nach generellem, sondern nach "wie machst du…" "was machst du…", "warum hilft… wenn du…" – Dinge, die mit Aktionen zu tun haben, und, noch besser, beobachtet werden können.</span> | |||
| Line 111: | Line 114: | ||
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> | |||
[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] | ||
| Line 119: | Line 123: | ||
* App Requirements | * App Requirements | ||
** accessibility is of prime importance, so the app have to be widespread to make the user downloading it. | ** accessibility is of prime importance, so the app have to be widespread to make the user downloading it. <span style="color:#598193">"accessibility" kenn’ ich nur von behindertengerechten Websites (muss aber nicht deshalb falsch sein). Wenn ich das richtig verstehe, geht es darum, dass eine App (bzw. deren Protokoll) weit verbreitet sein muss, damit man viele Leute erreichen kann?</span> | ||
** The app should be for free. | ** The app should be for free. | ||
** For the user it’s important to be up-to-date and flexible with messages. So he/she prefers an app for chatting. | ** For the user it’s important to be up-to-date and flexible with messages. So he/she prefers an app for chatting. | ||
| Line 137: | Line 141: | ||
** It would be useful to have a password for the app. | ** It would be useful to have a password for the app. | ||
** To feel safe, 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. <span style="color:#598193">Nur wenn ihr dazu auch Forschung/Daten habt: Was bedeutet das für die Nutzer, "immun vor Viren"? </span> | ||
** Important information, link, photos, videos, … are often sent by E-Mail. | ** Important information, link, photos, videos, … are often sent by E-Mail. | ||
** Distrust towards apps results e.g. from missing knowledge about safety and smart phone-apps. | ** Distrust towards apps results e.g. from missing knowledge about safety and smart phone-apps. | ||
| Line 156: | Line 160: | ||
It's hard and circular to login with one of your accounts, because there are too many steps until you are finally logged in. Moreover the buttons are difficult to find on the interface. | It's hard and circular to login with one of your accounts, because there are too many steps until you are finally logged in. Moreover the buttons are difficult to find on the interface. | ||
Therefore we want to create a new login-process. | Therefore we want to create a new login-process. | ||
<span style="color:#598193">Für die Verständlichkeit: Woher wisst ihr, warum der Login-Prozess schwierig ist? Eigene Erfahrungen, Usability-Test etc.</span> | |||
'''Plans – how we want to solve the problem(s)''' | '''Plans – how we want to solve the problem(s)''' | ||
--> Using the method: other application's test: | --> Using the method: other application's test: | ||
<span style="color:#598193">Ich freue mich, das ihr hier zusätzliche Methoden (Konkurrenzanalyse) angewandt habt. Das zeigt, dass ihr euch eigene Gedanken macht und eigene Lösungen sucht!</span> | |||
First we start to analyse the login process at other applications. | First we start to analyse the login process at other applications. | ||
| Line 203: | Line 210: | ||
<br> | <br> | ||
'''Version 2''' | '''Version 2''' | ||
<br> | <br> | ||
For the second iteration of our prototype we 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. | For the second iteration of our prototype we 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. | ||
<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 it's clear what your own status is and what's the status of your contacts. | <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 it's clear what your own status is and what's the status of your contacts. | ||
<br>We also added a 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 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. | ||
<span style="color:#598193">"For the second iteration of our prototype" Ist das wirklich eine ''Iteration'' und baut auf Erkenntnisse aus dem Text von Prototyp 1 auf oder eine parallel verfolgte Idee?</span> | |||
<br> | <br> | ||
| Line 220: | Line 231: | ||
In the next step we focused on improving the progress of creating an account. | In the next step we focused on improving the progress of creating an account. | ||
At this juncture we found it very importent 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. | At this juncture we found it very importent 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. | ||
<br>Therefore we added little info-buttons at situations in the app, that were trouble in our usability 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. | <br>Therefore we added little info-buttons at situations in the app, that were trouble in our usability tests | ||
<br>Furthermore we improved the design for the list of contacts once more and clearly seperated "online" and "offline" from each other. This two lists are know reachable with a kind of "tabs". | <span style="color:#598193">Die Formulierung ist schwierig. Wie wäre es mit: "We added info buttons near interface-Elements that were misunderstood in our tests, "</span>. 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. | ||
<br>Furthermore we improved the design for the list of contacts once more and clearly seperated "online" and "offline" from each other. <span style="color:#598193">Grund angeben: in order to…</span> This two lists are know reachable with a kind of "tabs". | |||
<br> | <br> | ||
<span style="color:#598193">Bezug zu Bildern herstellen (wie in der Mail angemerkt)</span> | |||
[[File:nutzerstudien_version3_1.JPG|200px]] | [[File:nutzerstudien_version3_1.JPG|200px]] | ||
[[File:nutzerstudien_version3_2.JPG|200px]] | [[File:nutzerstudien_version3_2.JPG|200px]] | ||
| Line 260: | Line 272: | ||
==Our conclusions== | ==Our conclusions== | ||
<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> | |||
Problems we had: | Problems we had: | ||