-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Usability testing w/ figma prototype #3
Comments
User 1 |
User 2 |
User 3 Name of participant: Shea Notes on Journey 1: Got to contact details Notes on Journey 2: Immediately knew to look to learn how to do car repair - seemed intuitive Q1: Good |
User 4 Name of participant: Sami Notes on Journey 1: I really like the name! Notes on Journey 2: Top navigation of search tab looks 'meh' Q1: - |
User 5 Name of participant: N/A Notes on Journey 1: Notes on Journey 2: The user notes that there are existing offline initiatives to tackle isolation/loneliness, and build community cohesion, e.g. local meetups advertised in certain locations Q1: No |
User 6 Name of participant: Josh (barman at The World's End pub) Notes on Journey 1: Assumed immediately that there must be monetary exchange involved Notes on Journey 2: Q1: - |
User 7 Name of participant: Yausin Notes on Journey 1: Notes on Journey 2: Q1: not unintuitive |
Name of participant: Maria Notes on Journey 1:
Notes on Journey 2:
Q1: Pretty intuitive. |
User 8 Notes on Journey: First impression on design - likes the design, name and font. Easy on the eye, cosy, not too stuffy, modern and casual, likes the lower case text, background looks like a Go board. Sign up screens - typo on "facilitating", strange language used, wording sounds like something they might see on a contract and be caught out on, also somewhat sexual. Perhaps "I am grateful" or "I will be grateful for the help I receive", "I intend to share my advice/help/experience freely". Feels good to press the commit button, doesn't like forms where you don't know how long they are. Our one does not have too much info, no address, phone number etc, makes them more inclined to sign up. Not enough contrast between background and form, a bit distracting and messy - it could be blurred or something. New skill/problem - not sure on what can be clicked ("Category" button"). Trust and Location should have size different and/or more spacing to be clear that one is part of the profile header. Wording is strange, "problems" has a negative connotation, perhaps "what I'm looking for" instead? Search - user easily navigated to the search function, took a while to figure out why "teach" and "learn" are different sizes, not clear that they're toggle buttons. Would be good to sort by distance. User profiles (from Search page) - would be nice to see the same icon next to the skill when you click on a result. More description wanted for skills and problems, maybe as a click-to-expand. Would like to click on the user picture and see more pictures, makes them seem more like a real person and trust them more. Consider integration of contact details with phone function (e.g. click to email app and phone apps). Aware of time constraint but in terms of contacting a user, a quick low-commitment way of sending a quick template message to the user would encourage contact and interaction. Own profile - unsure of what the + button does at first, in fact maybe no need to have this as a separate menu option. Could have it within profile as an "edit" button near the skills/problems. General - site is quite static, would expect to see some animations and interactivity on the final app. Q1: nothing else |
User 9 Landing page - Log-in button looks inactive. Having the background crosshatch lines over the form fields looks messy. On-boarding - off center commit buttons, maybe checkboxes instead of so many commits? Sign-up form - dots are very in the way. Order of the form is slightly weird, would have expected password last. Spacing is strange New problem/skill page - the + icon is not clear as to functionality. On first impression the page looks busy. The "category" looks like a button. "Problems" is not a nice sounding word. Perhaps "to teach" and "to learn"? Maybe "add" instead of "submit", submit sounds final and as if it would go to a different page after clicking. Profile - inconsistency in capitalisation. Delete button is too big, maybe just an X? "Trust" may make people think they would get murdered, maybe rename to "recommendations" or "endorsements". Is 2 trust good? Did they start from 10 and drop from there? But to be fair, a new user would see that they started on 0 trust. Star rating not necessarily good enough, as 2 x 5 star ratings is still not necessarily trust-worthy. How about a button that takes you automatically to search for the problem you've input? Search function - easily used map and icons on map. Did not see the "list" view at first. Would be good to view results by category rather than all results on user profile. Expects/prefers to see the list view first, rather than the map. Not sure what happened when they clicked on "make contact", presumes it already sent some sort of notification to the user that they're interested. If not, then perhaps change button to "see contact details"? Suggests some sort of template message for a user to quickly send, some people can be shy about messaging a stranger. Q1: nothing else |
Usability testing w/ Figma
Below is a script for running a usability testing session with a potential user, observing their interaction with our Figma prototype
Preamble
If they agree to take part
Journey 1
'Let's say you are a good cook. Using the app, can you create an account, find someone nearby who wants to improve their cooking skills, and find their contact details.'
Journey 2
'Let's say your car breaks down. Now that you've already registered on the app, can you log in, find someone to help you fix it, and find their contact details.'
Further questions
Templates for responses
Name of participant:
Where do they live:
Notes on Journey 1:
Notes on Journey 2:
Q1:
Q2:
Q3:
Q4:
Q5:
Q6:
The text was updated successfully, but these errors were encountered: