IFD:Nutzerstudien WiSe1314/Gruppe Anmeldung: Difference between revisions

IFD:Nutzerstudien WiSe1314/Gruppe Anmeldung (view source)

Revision as of 21:20, 17 December 2013

1,933 bytes added , 17 December 2013

no edit summary

Kede7290

53

edits

@@ Line 69: / Line 69: @@
 . Observation:
-Next week we want to make some usability tests of the app (ChatSecure) to find out how others deal with the login-process.
+Next week we want to make some usability tests of the app (ChatSecure) to find out how others deal with the login process. We want to find out if the log in process is intuitive for the user or not. So we get to know about user's handling with apps and their expectations. We hope to get suggestions and ideas for a better log in process based on the user's behavior.
 <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>
 '''Data Analysis & Main Results'''
 * App Requirements
-** The user wants an app/program which is used by a lot of people.
+** accessibility is of prime importance, so the app have to be widespread to make the user downloading it.
 ** 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.
 * Visual Design
-** The user wants a simple, intuitive, neatly arranged design, which looks uniform on all gadgets.
+** Complexity takes a lot of time, so you need a simple, intuitive, neatly arranged design, which looks uniform on all gadgets.
 * Interface & Functions
-**The user wants an interface, where you can see who is online at the moment and when a contact was online the last time.
+**It is handy for the user to have an interface, where you can see who is online at the moment and when a contact was online the last time.
-** The user wants to know if the chat partner read the messages.
+** The app should contain a function to let the user know if the chat partner read the messages because it faciliate the communication.
 ** The user wants to send out photos/videos.
-** The user wants to use a lot of smileys.
+** The user likes to express its emotion with a lot of smileys.
 ** The function "writes..." is not necassary.
 * Security
 ** It would be useful to have a password for the app.
-** The user wants to have a security warranty.
+** To feel save, the user desires to have a security warranty.
 ** It is important that apps are immune from viruses.
 ** Important information, link, photos, videos, … are often sent by E-Mail.
@@ Line 106: / Line 106: @@
 <div style="color:darkgreen">There are lots of "the user wants". It would be easier for outsiders to understand, if you could explain ''why'' the user wants this ('''if''' you know that. Naturally, my request is not asking for inventing explanations! If you only know that users ''want'' but not ''why'' you could make it subject of further research)</div>--[[User:JanD|JanD]] 19:58, 13 December 2013 (CET)
+<div style="color:blue">I tried to phrase and explain some points in another way. Is it ok? [M.E.]</div>
@@ Line 116: / Line 116: @@
 <div style="color:darkgreen">Nice proposal. Are you really talking about the log-in or about setting up a new (Jabber) account? Because in my experience it is not easy to set it up, but once you have your account working and data saved, it behaves very well. But please prove me wrong if that is a singular experience</div>--[[User:JanD|JanD]] 19:58, 13 December 2013 (CET)
+<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>
+'''Plans – how we want to solve the problem(s)'''
+Method 1: Other application's test
+First we start to analyse the login process at other applications.
+We found out that WhatsApp is the most widespread app to chat for our target group, second one is the Facebook messanger.
-'''Plans – how we want to solve the problem(s)'''
+. 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.
+. Facebook Messenger
+This application functions nearly the same way as WhatsApp, so you don't need a password to sign in.
+Our conclusion:
+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)
+Solution:
+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.
 [[File:Prototyp Anmeldeprozess.jpg|600px]]
 Our first prototype for the login process.