IFD:Nutzerstudien WiSe1314/Sicherheit endpresentation (security): Difference between revisions

IFD:Nutzerstudien WiSe1314/Sicherheit endpresentation (security) (view source)

Revision as of 19:56, 14 March 2014

1,146 bytes added , 14 March 2014

no edit summary

Hans

25

edits

@@ Line 20: / Line 20: @@
 [[File:NuStu_prototyping.jpg | 300px]] [[File:ideas.jpg | 300px]]
-<span style="color:#ee9966">I like that you started with very quick and raw sketches!  I think its important to generate lots of ideas in the beginning, so doing rough sketches is important.  I would like to see more sketches with all sorts of ideas from small makeovers to radical new ideas.</span>
+<span style="color:#ee9966">I like that you started with very quick and raw sketches!  I think its important to generate lots of ideas in the beginning, so doing rough sketches is important.  I would like to see more sketches with all sorts of ideas from small makeovers to radical new ideas.  Its also possible to do quick user tests with very rough sketches.</span>
@@ Line 195: / Line 195: @@
 To make the user keep an eye on the current security level, we added colour to the send button. This means the button has the same colour as the bar with the names of the contacts.
-'''EDIT''': So you know by clicking on the send button, whether the state is unsafe(red), safe(yellow) or safe and verified(green). You can also see the current status in the little lock above. But some test person told us, they dont look above by each sending of a message.
+'''EDIT''': So you know by clicking on the send button, whether the state is unsafe(red), safe(yellow) or safe and verified(green). You can also see the current status in the little lock above. But some test person told us, they don't look above by each sending of a message.
 [[File:pro.jpg | 900px]]
+<span style="color:#ee9966">Providing feedback where the user actually looks when working is key.  Its not always easy to tell that in advance, that's where user testing comes in.  So you got come valuable information in your test here.  One idea related to the coloring to consider: the app is called ChatSecure, so people expect secure messaging.  That expectation can be represented in the app, so when the messages are secure, the app looks like a "normal" Android messaging app.  Then use the color to represent when things are not secure.  That could make the non-secure states stand out more.</span>
 ===Protoype 2b)===
-A next question was how we could show that the message is not encryped. This also included the problem how one could start encryption.
+A next question was how we could show that the message is not encrypted. This also included the problem how one could start encryption.
 <span style="color:#598193">Warum habt ihr dieses Thema ("informing the user what is going on, if…") gewählt? Nutzerforschung? Vortest? Heuristik? Logische begründung, denn… (eure Erklärung)</span>
@@ Line 210: / Line 213: @@
 We discussed this idea in the group and decided that this would not be easy to understand. So we gave up this idea.
+<span style="color:#ee9966">This would be a very valuable thing to have for people using ChatSecure in high risk situations, where it is important that they don't mistakenly send messages insecurely.  An example is a journalist under surveillance from the state.  But for many people, it would just annoy them.  I wouldn't discard this idea so quickly, I think it could be made workable.  And it would work a lot better than a popup once the user learns it.</span>
 ===Protoype 2c)===
-We added a pop up, which appears when the user tries to start an unsecure chat or to remind the user to verify himself and/or his contact person.
+We added a pop up, which appears when the user tries to start an insecure chat or to remind the user to verify himself and/or his contact person.
 '''EDIT:''' The user have to choose, whether he will send the message unsafe or try a safe sending on another time. He also has the opportunity to save his response for all time. This can be changed in the settings.