A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | U1 | U2 | U3 | U4 | U5 | U6 | U7 | U8 | U9 | U10 | ||||||||||||||||
2 | Task 1 - Sign up | |||||||||||||||||||||||||
3 | Observaions | SSO preferred method of sign up/sign in, Very standard sign up | SSO preferred method of sign up/sign in, Very standard sign up | Noticed Google sign in which interested him, very standard sign up process | Would prefer to sign up via Google if available | Would prefer SSO for sign up/log in | If 'Skip for now' option available, he would tend to go with that option first before signing up to see if the app would be worth it | Would prefer to sign up via facebook or SSO | Would typically use SSO to log in | Would always prefer to sign in manually, very simple sign up process | Would prefer not to have a username because if the username she chooses is taken, it would stress her out | |||||||||||||||
4 | Ideas for Improvement | Add SSO screens | Add SSO screens | Add SSO Screens | Add SSO Screens | Add SSO screen | n/a | n/a | n/a | n/a | Remove username and just keep it at Name & email | |||||||||||||||
5 | Usability Issue | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |||||||||||||||
6 | ||||||||||||||||||||||||||
7 | Task 2 - Search, filter and bookmark a park | |||||||||||||||||||||||||
8 | Observations | After searching by location, she preferred to search via the map | "It reminds me of the Trip Advisor app". While looking through filters, he wasn't sure what the busyness section was for and skipped over it because he wasn't familiar with it. However, after he continued down the page and saw the Busy buttons and made the connection, then thought it was a really cool idea | Prefers interactive map to see parks. On main search page, initially thought you had to know to park name in order to search, didn't realize you could search by location. | Searching and filtering was similar to Yelp. ease of use rating 10, had no issues searching and filtering and bookmarking | Would prefer to search by map rather than list of parks. Very standard search flow, felt very familiar. Ease of use rating 10 | Skipped the search by location option and directly went to filter | Didn't search via location and went straight to filter. 10 rating for ease of use | Really apprecaited the horizontal scrolling. Search is very standard and familiar | Prefers searching via map view, easy for her to vizualize distance that way. Didn't utilize filter at all | When looking at Busy filter, "How busy is busy? How many dogs is that?" | |||||||||||||||
9 | Ideas for Improvement | Ensure interactive map is clickable | Move the Busy buttons above the slide bar | In search bar write "city" or "location" instead of name | n/a | n/a | n/a | n/a | n/a | n/a | Quantify levels of business | |||||||||||||||
10 | Usability Issue | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Ambiguous wording | |||||||||||||||
11 | ||||||||||||||||||||||||||
12 | Task 3 - Add a review | |||||||||||||||||||||||||
13 | Observations | Would read through user reviews and "thumbs up" if she agreed with what they said. Easy to find FAB. "How can you miss this big button here?!" Submitting review was very easy. "very standard" | Park page is very familiar--Reminds him of a Google page. Submitting review was very simple and familiar. Rated ease of use as 10 (extremely easy) | Able to find FAB quickly to submit review. Use of ease rating 10. "It was very standard" | Likes how there was parking information, but would prefer it be more specific. ie) parking lot, street parking, etc... Was able to submit a review without issues, very easy and familiar | Liked that parks page had a map, was wondering if it could be opened into Google Maps if tapped? Review submission was very easy, felt very standard like a Google review. | Overlooked the text field because there was no bordered text box to indicate where he was supposed to type | Overlooked the text field because there was no bordered text box to indicate where she was supposed to type | Submitting review was very standard and simple, 10 rating for ease of use | Submitting review was very simple and easy, no issues | Would like to have an option to submit a rating without having to write a review. If that isn't an option, she would just rather not submit anything | |||||||||||||||
14 | Ideas for Improvement | If no reviews, account for blank state | n/a | n/a | Add parking specifics, like yelp | Add link to open map in Google maps | Add a text box around all text fields | Add a text box around all text fields | n/a | n/a | Allow for rating only option as well | |||||||||||||||
15 | Usability Issue | n/a | n/a | n/a | n/a | n/a | user would skip the text field | User would skip the text field | n/a | n/a | n/a | |||||||||||||||
16 | ||||||||||||||||||||||||||
17 | Task 4 - Submit an Incident | |||||||||||||||||||||||||
18 | Observations | Adding and viewing incident was straightforward & easy. Noted that all the form fields were neccessary and important. Stated that it was good the app prompted her on what to write because if she were upset, she would have too many thoughts in her mind. (reduced cognitive load) | Submitting incident was easy and not complicated. Forms were helpful in determining what information to provide. | Able to utilize tabs to quickly jump to incidents section. Was able to submit an incident without any issues. All form fields were relevant information. Ease of use rating 10 | Was able to quickly determine breeds or problematic dogs by skimming through first few lines of information rather than reading entire posted incident. Likes how incident forms were structured well and asked for specifics to keep things separated. | Used top tabs to jump to incidents section, skimmed through top 2-3 lines which housed the breed and short description of problematic dog rather than reading through entire post. Found that very helpful. Submitting incident was very easy and low effort. Liked how he didn't have to think too much on what to write and just followed the prompts. | Noted that time should be approximate so that user doesn't feel obligated to know the exact time of when the incident occurred | It would be nice to allow other users to add comments when others post incidents. Perhaps people could be witnesses | Suggested to allow other users to comment or add photos on incidents in case people needed to look for witnesses | Wasn't sure whether the stated breeds and descriptions were about the posting users dog or the problematic dog. She had to read through the descriptions to determine that it was the problematic dog | Mentioned that asking for breed may be unneccessary because some people may mislabel the dog or even not know the breed at all. So she would rather just not have that and include the breed (if she knew it) in the description | |||||||||||||||
19 | Ideas for Improvement | n/a | n/a | n/a | n/a | n/a | include "approximate" | Include comment option | Include comment/photo upload option | n/a | Remove the breed dropdown | |||||||||||||||
20 | Usability Issue | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |||||||||||||||
21 | ||||||||||||||||||||||||||
22 | Task 5 - Submit an Update | |||||||||||||||||||||||||
23 | Observations | Had issues with date selection because she was not aware that she had to add an end date - found it unneccessary. Assumed there would be a date stamp by default once posted | Would have written about the park condition in his review, but since there is an update page, he would put it there. Struggled with date range, he didn't think adding a date would be relevant in this case because he assumes app would automatically add a date stamp | Initial thought would be to include park conditions in review, but because there was an update section, he would utilize that instead. Struggled with date range, but later admitted it was because he didn't read it. Said he thought having a start & end date would be useful. | Hesitated when date selection popped up, didn't expect to be asked to select a date range. He assumed that he would just select the day he encountered it and then add description | Date range was a bit confusing, she didn't realize there was already a defult date added & thought she was only supposed to select 1 date rather than a rage. Thinks the end date is irrelevant as she wouldn't know when the grass would clear up. Would just write what she thought in the description. | Although he was able to submit an update without issue, he asked if there could be a more obvious way for users to add an update | Updates didn't seem very evident to her, she had to go through the process of submittin an update in order to understand what it meant | Updates were very easy and straightforward to complete | Very easy to submit an update, originally didn't know what an update was but as she read through the posts she was able to make the connection | Wording "When is this happening?" confused her. Doesn't see the need for a date if there is a time stamp once it's posted | |||||||||||||||
24 | Ideas for Improvement | Remove "I don't know" option. Add a "confirm" button at bottom of page to confirm the defaulted (current) date | Completely remove date option and have defaulted date stamp once posted. Add a prompt / snack bar in review section to add an update? | Add a prompt / snack bar in review section to add an update? | Remove the date selection completely | Remove the end date all together | n/a | add a description or update to "Park update" | n/a | n/a | Remove date all together or reword | |||||||||||||||
25 | Usability Issue | Calendar pop up with date range too confusing. Simplify this or remove | Calendar pop up too confusing | Calendar pop up too confusing | Calendar pop up too confusing | Clanedar pop up too confusing | n/a | n/a | n/a | n/a | n/a | |||||||||||||||
26 | ||||||||||||||||||||||||||
27 | ||||||||||||||||||||||||||
28 | ||||||||||||||||||||||||||
29 | ||||||||||||||||||||||||||
30 | ||||||||||||||||||||||||||
31 | ||||||||||||||||||||||||||
32 | ||||||||||||||||||||||||||
33 | ||||||||||||||||||||||||||
34 | ||||||||||||||||||||||||||
35 | ||||||||||||||||||||||||||
36 | ||||||||||||||||||||||||||
37 | ||||||||||||||||||||||||||
38 | ||||||||||||||||||||||||||
39 | ||||||||||||||||||||||||||
40 | ||||||||||||||||||||||||||
41 | ||||||||||||||||||||||||||
42 | ||||||||||||||||||||||||||
43 | ||||||||||||||||||||||||||
44 | ||||||||||||||||||||||||||
45 | ||||||||||||||||||||||||||
46 | ||||||||||||||||||||||||||
47 | ||||||||||||||||||||||||||
48 | ||||||||||||||||||||||||||
49 | ||||||||||||||||||||||||||
50 | ||||||||||||||||||||||||||
51 | ||||||||||||||||||||||||||
52 | ||||||||||||||||||||||||||
53 | ||||||||||||||||||||||||||
54 | ||||||||||||||||||||||||||
55 | ||||||||||||||||||||||||||
56 | ||||||||||||||||||||||||||
57 | ||||||||||||||||||||||||||
58 | ||||||||||||||||||||||||||
59 | ||||||||||||||||||||||||||
60 | ||||||||||||||||||||||||||
61 | ||||||||||||||||||||||||||
62 | ||||||||||||||||||||||||||
63 | ||||||||||||||||||||||||||
64 | ||||||||||||||||||||||||||
65 | ||||||||||||||||||||||||||
66 | ||||||||||||||||||||||||||
67 | ||||||||||||||||||||||||||
68 | ||||||||||||||||||||||||||
69 | ||||||||||||||||||||||||||
70 | ||||||||||||||||||||||||||
71 | ||||||||||||||||||||||||||
72 | ||||||||||||||||||||||||||
73 | ||||||||||||||||||||||||||
74 | ||||||||||||||||||||||||||
75 | ||||||||||||||||||||||||||
76 | ||||||||||||||||||||||||||
77 | ||||||||||||||||||||||||||
78 | ||||||||||||||||||||||||||
79 | ||||||||||||||||||||||||||
80 | ||||||||||||||||||||||||||
81 | ||||||||||||||||||||||||||
82 | ||||||||||||||||||||||||||
83 | ||||||||||||||||||||||||||
84 | ||||||||||||||||||||||||||
85 | ||||||||||||||||||||||||||
86 | ||||||||||||||||||||||||||
87 | ||||||||||||||||||||||||||
88 | ||||||||||||||||||||||||||
89 | ||||||||||||||||||||||||||
90 | ||||||||||||||||||||||||||
91 | ||||||||||||||||||||||||||
92 | ||||||||||||||||||||||||||
93 | ||||||||||||||||||||||||||
94 | ||||||||||||||||||||||||||
95 | ||||||||||||||||||||||||||
96 | ||||||||||||||||||||||||||
97 | ||||||||||||||||||||||||||
98 | ||||||||||||||||||||||||||
99 | ||||||||||||||||||||||||||
100 |