User experience test - results #4264
Replies: 6 comments 25 replies
-
Wording is already "single garage" and shows a picture of one car. A garage for two cars (on the grounds of a detached house) would still count as a "single garage" too, so a description like "Garage for a single car" would not be correct. I think it is fine / low priority.
Well, what is done now is to show the "tap here" hint, as known from other apps. (The ripple.) That is hopefully a good hint for many to just try to tap it. When they tapped it, hopefully they would get it because it is WYSIWYG. Another solution would be to disable all those quests (sidewalk, cycleway, ...), which is something I thought about anyway for all quests where there is also a layer that does the same. (Because using the layer would be more efficient and would be the preferred way to do it.)
See above, it could be disabled because there is a layer.
Ok. Needs description that should mention that it is time-consuming and sometimes difficult to answer (if such a description does not exist yet). But anyway, can you link to the issue/discussion where your prior suggestion was rejected? Maybe I forgot some good arguments to keep it enabled by default.
But it does not really occur that often, does it? And it occurs for probably relatively large areas, so it's not spamming the view in that sense. |
Beta Was this translation helpful? Give feedback.
-
|
Ok, then maybe the orchard one can also be disabled by default. |
Beta Was this translation helpful? Give feedback.
-
For me the ripple effect only plays when I release a lane after tapping, but only then. It doesn't play after opening the quest's menu and just waiting. |
Beta Was this translation helpful? Give feedback.
-
|
For me it (one side slowly getting darker and then brighter again, then the same for the other side) only shows the first time opening such a quest dialog after starting StreetComplete. Is this intentional or a bug? |
Beta Was this translation helpful? Give feedback.
-
|
That's right, this is what actually happens. The animation is showing for me too, but only once, and it does not repeat if I reopen the quest or if I open a different instance of this quest, but only an app restart. |
Beta Was this translation helpful? Give feedback.
-
|
It's intentional. It only shows the first time. |
Beta Was this translation helpful? Give feedback.
-
Virtually all of my friends and family wonder why I bother with doing this a lot of the time. Some things make sense, like adding whether a parking lot is paid: that's something they would like to see on a map. A lot of other things make sense if you think for two seconds: we might not care about kerb heights, but wheelchair users do. Wheelchair is never mentioned in that quest. And then there is the category where I also have no idea myself, like building stories and roof shape. (I've got those disabled.) Is that for 3d renders? You'd still not know in which orientation the roof is and I usually can't see the backside so I'd just be guessing about that part. What about stairs' step count: who could use that data? Would there be an app that lets you set a cut-off point for how many steps you're willing to walk before it tells you there is no path to the destination? Wouldn't the elevation difference be more important (tall steps are more exhausting) and way easier to obtain (for entire countries at once, rather than individual stairs' data)? Not everyone cares to hear my guess/assumption that things like road surface go into routing algorithms as tie-breaker (seems unimportant to answer for every single piece of road, iff that's the only purpose), but even with people that care, I can't explain many quests' importance adequately. Having template answers, either for myself or to answer questions, would be quite nice. Seeing more value might also lead to more contributions. This could tie in with info on how to use the quest (like the sidewalk, cycleway UI). Such a pop-up page could also give more info about the different options that didn't fit into the main UI, common pitfalls, and/or info shown for expert users to say which button corresponds to which tag value (when I was new to the app, I would sometimes know which tag to use but not which image to click for that; other times, I'm just curious to learn how to tag something outside of SC). A question mark in the corner of each quest, which opens that info page in a local HTML view thing, could lead people to this extra info. I'd be happy to research and contribute this information for each quest in case this would be something you decide is a good idea.
Would these people be mappers under other circumstances? This seems a little extreme 😅 |
Beta Was this translation helpful? Give feedback.
-
I still remember how confused I was by some things when I was starting to map! Though yes, some of this people were not really interested in mapping and wanted to help me or were bribed with ice cream (like my younger sister and her friends). So average SC mapper is likely less confused. But especially
Yes, and floor count may be used to identify building type and as proxy for population density.
Navigation for blind people would be able to announce how many steps are expected. And routing can detect and assign lower penalties for steps with very low density (200 m of
For routing |
Beta Was this translation helpful? Give feedback.
-
Can you also bribe me please? 😄
I was thinking that no road would be reasonably considered for routing anyway if it's cobblestone or sand, they'd not be the path that most people travel and so not even qualify for highway=tertiary and so the router never picks it anyway. But yeah for something like cycling, it might not be so picky and go for shorter routes rather than fewer turns / higher maxspeeds. If that ends the cyclist up on a sandy road that is impossible to cycle on, they would indeed curse the router :P I've added a little section here experimentally. Do you think it's a good idea to collect these on the wiki? Whether it eventually ends up inside SC on an info card is less important then. https://wiki.openstreetmap.org/wiki/Key:surface#Uses I'm not entirely sure about this setup, maybe a central page makes more sense. Perhaps it could have it reversed: per goal (like routing) it might have an itemized list of tags used for it (and on that line, you can also specify how/why if it's not necessarily obvious). |
Beta Was this translation helpful? Give feedback.
-
LIt quest
What does it mean they entered it wrong? I personally just look whether there is a lamp and if so, yes. Maybe I look whether it has this red sign thing, then I know (because I have learned it through StreetComplete!) what to do, but otherwise "Yes". |
Beta Was this translation helpful? Give feedback.
-
|
I guess they did this, because they think the lamps need to be nearby/next to the street, instead of checking that the way is actually somewhat lit i.e. and thus passable at night. Another solution would thus be to change the text to focus of the question asked to sth. like this:
(variant 0) Variant 1would also allow the red-sign thing and make users aware there is an "other answer" they may need to chose:
(longish text though) Variant 2Also note we may wanna not make it that strong/confusing, as other factors may include whether it is passable
Also "passable" may be the rong term here I dunno. Or so. |
Beta Was this translation helpful? Give feedback.
-
|
"Is there enough lighting to see well on a dark night". Many people including myself interpret the current quest as does this way have it's own dedicated lights, regardless of if they actually do a good job at lighting the way or if there is nearby lights spilling over. |
Beta Was this translation helpful? Give feedback.
-
|
I don't know if the word "passable" is applicable here, as virtually everyone carries a portable flashlight nowadays. Sure you can pass it, not like it floods overnight, but what is really being asked is whether there is light to see by available there. Andrew's suggestion sounds good to me, but your interpretation of the quest is... I want to say "wrong", but honestly it's a valid interpretation of the quest text, just not what the
I think it's broad enough to mean: whether the object is lit up at night, by whatever light (be it belonging to the object itself, such as a bus stop, or a light in the vicinity that shines sufficiently on the object and isn't likely to change in the future). |
Beta Was this translation helpful? Give feedback.
-
|
The quest and the wiki description are very good in their brevity, but where can one find help for interpretation? For me it would help if there were an assistent asking even simpler questions along a flow-chart like decision tree and guiding me to the right answer. In case of the lit-quest an assistent could ask for the presence of nearby lamps showing some examples (lamps along the way, nearby lit expressway, lamps hanging on wires between buildings and so on), then ask if it is lit all the night and so on. I personally couldn't find any advice of this kind even on the web. Hence it is sometimes a very time consuming intellectual task to get the question and the expected result right. |
Beta Was this translation helpful? Give feedback.
-
|
If you can improve wiki documentation that would be highly welcome! If you have good examples of photos where it is unclear how to make tagging you can also post it on the talk page of OSM Wiki. There were also some ideas how to implement such mini tutorial in StreetComplete, I think there is an open issue concerning it. |
Beta Was this translation helpful? Give feedback.
-
|
+1 for disabling the building levels quest by default. It took me a while to find that some quests can be turned off and the building levels bubbles obscure what I think could more usefully be collected by SC. Around me, most roads are long terraces of identical height buildings, recording their height is much more efficiently done with a bulk select in JOSM.
|
Beta Was this translation helpful? Give feedback.
-
|
As to your suggestion regarding opening hours:
If you mean that M-F are already checked by default: This is already the case. Actually, even better, it checks the workdays of the week, e.g. in Iran it is Sa-Th. In different countries, there are different workdays.
This is already the case.
Possible. But awkward for businesses that e.g. only open in the evening. Even if you just cover 6:00 to 10:00 as starting times, with a 30 minute interval, you have 10 buttons in that dialog, that may be a bit too much. It's only a few buttons less that the numerical input keyboard usually has. Also, what about shops that close for lunch in EveryDoor? Before doing any experiments here, maybe it would be more prudent to focus on #3796 |
Beta Was this translation helpful? Give feedback.
-
|
Commenting on the opening hours input dialogues, I much prefer SC over ED because the correct hours interval is rarely any of the ones ED suggests, so I pretty much always have to hit the "more hours" (or something) button. (I haven't been counting but I would say less than 1/10) I also find that the hours/minutes are a lot harder to find on ED than on SC exactly because it doesn't use a clock looking thing. Sure it's sorted and all, but I don't want to be binary searching the thing. In short, the SC clock thingy feels a lot more natural to use the ED, and ED rarely suggests the interval I'm looking for. And it's a lot of ckicking like @westnordost said. |
Beta Was this translation helpful? Give feedback.
-
Is it? I can click "add opening hours" once again, and select "Add days of the week", but days which don't yet have opening hours defined are not checked by default. |
Beta Was this translation helpful? Give feedback.
-
|
I'm a bit sad that building level quest was disabled by default :( |
Beta Was this translation helpful? Give feedback.
-
|
You can already skip quests via "Other answers …" → "Can't say" → "Skip". And, just for the record, you can still manually re-enable the building levels quest (and others) in the settings. |
Beta Was this translation helpful? Give feedback.
-
|
ah, I thought I need to write some note if I want to skip it, but I see it's not necessary... ignore my comment then. |
Beta Was this translation helpful? Give feedback.
-
Maybe the lanes could slowly blink, gradually change the brightness of their background, or something similar, so it would call attention at the detail that the lanes are to be clicked. In case you do this, I think the different lanes should blink separately (e.g. delayed, or one lane blinking at a time, maybe the blinking can be semi-random so that a lane blinks every 5-10 seconds).
I think this might be a problem for all quest types.
Some thoughts of mine: In my country it is unusual to have the same opening hours for saturday as for weekdays, so having saturday ticked here does not make much sense. When on the go, I have problems with the time picker dialog. Also, this quest has important very specific options in the "other answers..." menu, one of which can be "correctly" specified by selecting the proper timeframe. I can easily imagine that users are picking 0:00-0:00 for every day instead of using 24/7, or since they don't know they can input differing opening hours by month they simply just input the opening hours that applies to the month when they surveyed.
Personally I think it's also sometimes hard to decide on what should I select at night, as some streets have street lighting, but lights are rare enough that between every 2 lights there are several meters on the road that is very dark, so much so that I wouldn't feel safe riding my scooter at normal speeds there because I wouldn't be able to see where is the road damaged, or if theres some other obstacle. |
Beta Was this translation helpful? Give feedback.
-
where the quest is located I think it is defined at https://github.com/streetcomplete/countrymetadata/blob/master/data/workweekDays.yml |
Beta Was this translation helpful? Give feedback.
-
I also have this way too often. It used to be better in previous versions (long ago)... I think it was changed either as part of upgrading dependencies, or as part so solving some issue. |
Beta Was this translation helpful? Give feedback.
-
It's in Hungary, which is usually abbreviated as HU. I don't see it defined in that file. Maybe something else is going on here?
Oh, so the reason I wasn't able to reproduce it is that it got fixed. That's good to hear, thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Yes, @matkoniecz linked the wrong file: https://github.com/streetcomplete/countrymetadata/blob/master/data/regularShoppingDays.yml |
Beta Was this translation helpful? Give feedback.
-
I again run an UX test on a small sample of ten people, and reviewed OSM notes, posted discussions and SC-related topics in attempt to find similar feedback.
I tried to fix/report what I found as a separate issues but taking additional actions or creating separate actionable issues may be worth doing based on the info here. Feel free if you notice that something like that is missing.
Note: UX sample was small, biased and not representative of anything except how willing they were to help me. Nevertheless I learned or relearned multiple things. Tests were done almost entirely during Winter and Spring.
Overall, there is a noticeable improvement compared to what people expressed previous UX testing. Some people were tested again (they participated in #1470 testing round) and they noted, unprompted, noticeable improvements.
Testing was a bit less productive - because number of issues encountered by new mappers was noticeably lower.
One of the received comments was
Nevertheless, multiple new issues were spotted and many were fixed.
Other selected comments (also translated):
Some people expressed doubt and confusion about some quests "why this info is collected?". The only serious negative comments that were appearing were complaints about (1) collecting very unimportant data and (2) heavy battery use.
Reminder, especially to me and @westnordost : regular people are confused among things which are obvious to OSM mappers.
For example, multiple people idependently asked about additional hints that would help to distinguish between various surface values as they were really unsure - and some of them made mistakes.
Some test mappers failed to distinguish flat and gray
surface=dirtfromsurface=concrete! Not sure how much SC can help here, that is case of skills which not really used in general.The single garage also needs an explanation (selected where building=garages was more fitting). Maybe show also
=garagesin the initial top values prefill. Or do not show=garagethereRegular people are confused by many this that seem obvious to people tagging them for a long time.
"Oh, so these dots before crossings are for blind people" "oh so that is why traffic lights are beeping"
I observed one person entering wrong bicycle parking capacity, reading the hint and correcting it.
So in case of doubt, I would rather add an extra explanation.
One of the mappers in the kerb height selection quest selected one that was matching by material - not by height. (concrete vs stone)
On asking why they did this they noticed the problem.
Show all quests for an element at once (#124) was the top requested change by people - in various forms. "autoopen next quest if the element has multiple quests" or "show all tasks for the element" were the most common. Sadly, I do not really have an idea how to do this well.
The road tap interface (sidewalk quest, cycleway quest) is the second most confusing part of SC
https://github.com/streetcomplete/StreetComplete/discussions/33643364 - specifically about the incline quest (this part is fixed!)
People are highly confused by it. Out of 7 people who encountered it - 7 were confused. One managed to forget how to use it within a few days and was confused again when we tested the app again. One person out of 7 managed relatively quickly to discover how to use it - and they are also a programmer and proceeded to debug the form.
How to solve it?
Show crude popup "click here"?
A colourful bubble on the sidewalk itself "click me"?
Show the message below the question explaining how this interface should be used?
Show popup for new users?
Design a completely new interface? Especially #2684 seems interesting and worth considering, but that would leave the cycleway and sidewalk surface even more unique and confusing...
Lane selection for double no like with sidewalks or cycleways is extremely confusing. People are regularly confused that "no" should be selected at all and that it should be done on both sides of the road.
Often not even reaching "can't say', some selected no for one side and considered the question as answered - and were confused about what they should do now.
I was pessimistic about the usability of the opening hours editor, but people used it without a real trouble. Also for resurvey quests.
I was pessimistic about the lit quest during the day but it turned even worse: every single tested person who encountered
litquest during day was confused, many people were entering the wrong data when surveying during the day.I would strongly support moving it to an overlay-only task. Or get back to disabling it during the day, with an option to override it by power users.
Right now is is the most confusing part of StreetComplete.
One of the universally observed things: surveying building levels is really confusing, time-consuming and dominates other tasks.
It is quite depressing to see how much effort is getting consumed by this quest.
I would seriously consider disabling it by default. This quest is confusing, extremely time-consuming, with limited benefits, often unclear or hard to answer and boring.
It is quite sad to see how much effort it consumes, its enablement by default is likely discouraging potential mappers, and overall reducing the value of quest mapped. Disabling it by default would result in an immediate drop, but I expect that overall greater retention would be helpful - especially when quests would be weighted by value).
I know that I proposed disabling it by default already and it got rejected but after testing I am really sure that it would be a good idea.EDIT: this appears to be wrong, it seems I have never proposed it
EDIT2: see #3295 for examples of problems with classifying building level count
EDIT3: disabled in 0bcd6d7
Also, the orchard quest is really hard to answer. I am above average among city dwellers in plant recognition and I can identify several common plants (including wheat/rye/etc from each other). But I am unable to differentiate between pear trees and apple trees. And cherry trees.
Also, none of the people who run into the orchard quest could answer its question.
I think that it is another candidate for being disabled by default.
EDIT: orchard quest disabled by default in edb8a9d (it can be still enabled if you want to solve it!)
It is not clear that the building=* quest is not asking about current use. Or about the most prominent public use. People keep misinterpreting this question and look through entries and comment "there is no entry here for greengrocer" when they see an apartment building with a greengrocer at the floor level. I do not have a good idea how to improve things further here.
I was pessimistic about the usability of the opening hours editor, but people used it without real trouble. Also for resurvey quests.
implemented:
including things reported by others and treated with higher priority as a result of UX search such as Don't ask about toilet fees in Canada or US #4174
reported and implemented by others:
rejected:
stuck:
not counted as part of UX work time for grant purposes, but still a direct result of UX investigation:
My work on UX testing was sponsored by a NGI Zero Discovery grant.
See #1470 for the previous one.
Beta Was this translation helpful? Give feedback.
All reactions