https://github.com/streetcomplete/StreetComplete/discussions/4264 Skip to content Sign up * Product + Features + Mobile + Actions + Codespaces + Copilot + Packages + Security + Code review + Issues + Discussions + Integrations + GitHub Sponsors + Customer stories * Team * Enterprise * Explore + Explore GitHub + Learn and contribute + Topics + Collections + Trending + Skills + GitHub Sponsors + Open source guides + Connect with others + The ReadME Project + Events + Community forum + GitHub Education + GitHub Stars program * Marketplace * Pricing + Plans + Compare plans + Contact Sales + Education [ ] * # In this repository All GitHub | Jump to | * No suggested jump to results * # In this repository All GitHub | Jump to | * # In this organization All GitHub | Jump to | * # In this repository All GitHub | Jump to | Sign in Sign up {{ message }} streetcomplete / StreetComplete Public * * Notifications * Fork 261 * Star 2.9k * Code * Issues 91 * Pull requests 8 * Discussions * Actions * Security * Insights More * Code * Issues * Pull requests * Discussions * Actions * Security * Insights User experience test - results #4264 matkoniecz started this conversation in Feedback User experience test - results #4264 @matkoniecz matkoniecz Aug 2, 2022 * 4 comments * 14 replies Return to top edited [899] matkoniecz Aug 2, 2022 Collaborator - 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 I am unsure is there a point in meeting, I installed app and everything is clear Nevertheless, multiple new issues were spotted and many were fixed. Other selected comments (also translated): Repeating recent used level in building level quest is great Classifying and filling forms is too similar to my job and I would never do this as a hobby This link collection is great, I discovered some projects thanks to it 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=dirt from surface=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 =garages in the initial top values prefill. Or do not show =garage there Regular 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 lit quest 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). [S: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.:S] 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: * stop asking for roof shape by default stop asking for roof shape by default #3161 stop asking for roof shape by default #3161 * crossing=unmarked is causing a severe confusion (some actions taken, effects to be reviewed furing future testing) #3341 - discussed with some actions taken (for example replacing the image of unmarked crossing). Maybe more needs to be done, let's see how changes done will affect users. * small tweaks: is crossing chicane similar to one on this photo? Or to the depicted one? [image in SC changed] #3635 ask better about cancelling cancellation, fixes #3396 #3443 remove crossing from crossing type answers #3383 make text more readable - set style on image descriptions used in some quests #3328 a8b73d7 parking access - easier tapping #3427 remove wall-of-text effect #3402 new images for parking lot and unmarked crossing #3421 minor adjustment to setting building properties #3390 make rejecting cancellation more clear #3576 462e287 Consider officially archiving other branches? streetcomplete-mapstyle#130 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 * other minor upstream tweaks: Support building=manufacture with dedicated building description openstreetmap/id-tagging-schema# 523 ( building=manufacture with own building description openstreetmap/id-tagging-schema#524 ), add two popular building values openstreetmap/id-tagging-schema#528 * popular unsupported values of major keys openstreetmap/ id-tagging-schema#529 was done to ensure that SC is not affected by other similar issues (though nothing major was found) * improving styling of the ranking page (Make statistics menu less sad - decorations and colour #4203 Make statistics menu less sad - more interesting display of data (colours? patterns?) #3414) was a result of previous UX tests * Multiple improvements in Polish translation (typos, misleading translations, tortured grammar, inconsistent terminology) * this quests are useful also for cyclists #4246 (minor achievement tweak) and buildings type selection in one list #4215 Building type quest - allow to access full list by scrolling, not by clicking "show more" #3387 (surprisingly time-consuming building quest interface improvement, still definitely worth it) are implemented but still in the PR phase * handle surface vs tracktype conflicts #4105 and https:// josm.openstreetmap.de/ticket/22102#comment:9 - better tracktype-surface conflict handling in JOSM (merged!) and StreetComplete (in the PR phase) * Parking access - publicly available private parkings [implemented in #3473] #3429 reword parking access - #3429 #3473 - better description for parking quest * probably something else which I missed * https://taginfo.openstreetmap.org/projects/streetcomplete#tags - taginfo listing (Taginfo listing of tags added or modified by StreetComplete #4225) * better images for ramp quest (partially done for copyright-related results - but see also https://github.com/ streetcomplete/StreetComplete/blob/ 7d5ab65024a057f23eab9325c73088239097ac6b/app/src/main/res/ drawable-xxhdpi/ramp_bicycle.jpg vs https://github.com/ streetcomplete/StreetComplete/blob/ 55287f240eee2d06cf9a47629c69094b71b90b67/app/src/main/res/ drawable-xxhdpi/ramp_bicycle.jpg ), with time on this split between this tasks reported and implemented by others: * Maybe railways in dark mode are too prominent streetcomplete-mapstyle#107 * Also, triggered fix in a proprietary (but replaceable) dependency ( via Render natural=grassland like landuse=grass (impossible, missing in Jawg) streetcomplete-mapstyle#108 ) rejected: * stop asking crossing detail for unmarked crossings #3394 stop asking crossing detail for unmarked crossings * Provide extra info allowing to identify specific object such as bicycle parking #4058 Provide extra info allowing to identify a specific object such as bicycle parking * put address quests higher #4172 move address quest higher in the list to make more clear that important data is also being asked about stuck: * Surface tagging - difference between "ground" and "unpaved" is unclear #3440 (change "Ground (generic)" to "Natural ground"? But that will encourage using it instead of more specific values) * Link specific tag pages on OSM Wiki #3442 - linking used tags. Doing this properly requires listing tags used by StreetComplete (which also enables taginfo project listing). This one turned out to be surprisingly complex! Taginfo listing of tags added or modified by StreetComplete #4225 was implemented partially to enable it - but it revealed some issues in how OSM Wiki handles compound tags and some things need to be resolved there first before such linking will be a good idea. See https:// wiki.openstreetmap.org/wiki/Talk:Wiki# Redundant_pages_for_%22building_block%22_tags ("Enhanced not-found messages for non-English users" and "name:mos" sections are relevant blockers) not counted as part of UX work time for grant purposes, but still a direct result of UX investigation: * Support subject:wikidata and subject:wikipedia for historic= memorial and tourism=artwork and information=board openstreetmap/ id-tagging-schema#533 Describe traffic_calming=yes as "Unspecific traffic calming value" openstreetmap/id-tagging-schema#547 Complain about "Unspecific primary tag value" (like barrier=yes) in validator openstreetmap/iD#9209 Describe barrier=yes as "Unspecific barrier value" and complain about it in validator openstreetmap/id-tagging-schema#531 Complain about "Unspecific primary tag value" (like barrier=yes) in validator openstreetmap /iD#9209 (comment) * triggered multiple edits in Poland to reduce variants of names in operator tags for ATMs (editing time here was not counted toward UX work, so it was not a paid editing) --------------------------------------------------------------------- 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. 7 You must be logged in to vote 10 [?] 8 Replies 4 comments * 14 replies Oldest Newest Top [466] westnordost Aug 3, 2022 Maintainer - The single garage also needs an explanation (selected where building=garages was more fitting). Maybe show also =garages in the initial top values prefill. Or do not show =garage there 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. The road tap interface (sidewalk quest, cycleway quest) is the second most confusing part of SC How to solve it? A colourful bubble on the sidewalk itself "click me"? 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.) I was pessimistic about the lit quest during the day but it turned even worse: every single tested person who encountered lit quest during day was confused, many people were entering the wrong data when surveying during the day. See above, it could be disabled because there is a layer. 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. 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. Orchard I think that it is another candidate for being disabled 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. 3 You must be logged in to vote 4 replies @matkoniecz edited matkoniecz Aug 4, 2022 Collaborator Author - 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. Apparently I was misremembering. I should have linked it from start as it appears to be not existing. I found only #3169 which was about power poles. 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. It happens often enough that I have decided to test SC only in the city to avoid running into this question (I guess I could also disable in on the phones used by testers...). At least in my area there is large number of orchards that are half-abandoned/abandoned but still existing. And it is not getting better for modern industrial orchards, as these are rarely signed with info what they produce and types of trees are not recognizable at all. https://overpass-turbo.eu/s/1kIT - note that I am quite often in this area, I am trying to answer SC quests and still orchard quest remains not answered there :( screen24 Well, what is done now is to show the "tap here" hint, as known from other apps. (The ripple.) Yes, I know. Sadly people are not really noticing it. I think it is fine / low priority. I agree, it mostly goes on pile "remember that people are more confused that you would expect" Beta Was this translation helpful? Give feedback. @matkoniecz edited matkoniecz Aug 4, 2022 Collaborator Author - Ok. Needs description that should mention that it is time-consuming and sometimes difficult to answer (if such a description does not exist yet). override val defaultDisabledMessage = R.string.default_disabled_msg_difficult_and_time_consuming gives This quest type is disabled by default because it is either time-consuming or difficult to make the right choice. Only enable this quest type if you are really committed to adding this kind of data. I plan on applying it in a few days, unless someone convinces me otherwise. Beta Was this translation helpful? Give feedback. @matkoniecz matkoniecz Aug 4, 2022 Collaborator Author - 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.) Actually, sidewalk one works mostly fine and I would consider keeping it. But I would disable lit quest by default, while allowing users to reenable it if they want. I also plan on doing this, though here a new message may be needed to say something specifically about difficulty of solving it during the day. Beta Was this translation helpful? Give feedback. @westnordost westnordost Aug 4, 2022 Maintainer - Ok, then maybe the orchard one can also be disabled by default. Beta Was this translation helpful? Give feedback. 2 [562] lgommans Aug 9, 2022 - 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. 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. --------------------------------------------------------------------- Some test mappers failed to distinguish flat and gray surface= dirt from surface=concrete I observed one person entering wrong bicycle parking capacity, reading the hint and correcting it. 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. every single tested person who encountered lit quest during day was confused Would these people be mappers under other circumstances? This seems a little extreme And please don't make lit day-only again, I'm not often driving on public transport at night since it doesn't exist here (sad), so I wasn't getting anything done whereas I can recognize a street lantern-lined street during the day just fine... If need be, an expert option here would work for everyone, though if I wonder about it being patronizing and if the real target audience would understand this more intuitively. Beta Was this translation helpful? Give feedback. 3 You must be logged in to vote 2 replies @matkoniecz matkoniecz Aug 10, 2022 Collaborator Author - Would these people be mappers under other circumstances? This seems a little extreme 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 lit quest was confusing even to people who had no problem with other things :/ 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? Yes, and floor count may be used to identify building type and as proxy for population density. What about stairs' step count: who could use that data? 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 highway=steps, only 20 step_count). And wheelchair routing can also allow for example step_count=1 and step_count=2. Not everyone cares to hear my guess/assumption that things like road surface go into routing algorithms as tie-breaker For routing surface=unhewn_cobblestone and surface=sand is not only tie-breaker :) Beta Was this translation helpful? Give feedback. @lgommans lgommans Aug 11, 2022 - bribed with ice cream Can you also bribe me please? For routing surface=unhewn_cobblestone and surface=sand is not only tie-breaker :) 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. [119] rugk Aug 10, 2022 - LIt quest I was pessimistic about the lit quest during the day but it turned even worse: every single tested person who encountered lit quest 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. 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. 2 You must be logged in to vote 6 replies @rugk edited rugk Aug 10, 2022 - 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: Is this way passable at night? A way is passable at night if it is lit by nearby lamps or other light sources. (variant 0) Variant 1 would also allow the red-sign thing and make users aware there is an "other answer" they may need to chose: ** Is this way passable at all night?** A way is passable at night if it is lit by nearby lamps or other light sources all the night. Note signs may show when it is not lit the whole night. (longish text though) Variant 2 Also note we may wanna not make it that strong/confusing, as other factors may include whether it is passable Is this way lit and [thus] passable at night? If a sign indicates it is not lit the whole night, please choose an answer at "other answers". Also "passable" may be the rong term here I dunno. Or so. Beta Was this translation helpful? Give feedback. @andrewharvey andrewharvey Aug 11, 2022 - "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. 3 @lgommans edited lgommans Aug 11, 2022 - 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 lit tag means. Wiki says: indicates the presence of lighting 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. 1 @mamoffel mamoffel Aug 20, 2022 - 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. @matkoniecz matkoniecz Aug 20, 2022 Collaborator Author - @mamoffel 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. View more [726] milh0use Aug 14, 2022 - +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. Regarding editing opening times, the easiest I've found is in Every Door, it uses several common defaults that make entry really quick, such as: * default days M-F (checkboxes), opening time as a tap on 06:00, 06:30, 07:00, 07:30...09:00, 09:30 or custom (pick an hour, then pick minutes past that hour), closing time as another list of half hourly times from 16:00-19:00 or custom, and when you've entered the first rule, if any days were unchecked it prompts you for a second rule with those missing days selected, and you can choose "closed" or go through the whole opening time/closing time process again. Process continues until every day of the week is covered by a rule. Beta Was this translation helpful? Give feedback. 2 You must be logged in to vote 2 replies @westnordost edited westnordost Aug 15, 2022 Maintainer - As to your suggestion regarding opening hours: default days M-F (checkboxes) 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. and when you've entered the first rule, if any days were unchecked it prompts you for a second rule with those missing days selected This is already the case. opening time as a tap on 06:00, 06:30, 07:00, 07:30...09:00, 09:30 or custom 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. @siiky siiky Sep 1, 2022 - 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. Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment Category Feedback Labels None yet 8 participants @matkoniecz @andrewharvey @westnordost @lgommans @milh0use @rugk @siiky @mamoffel Add heading text Add bold text, Add italic text, Add a quote, Add code, Insert Link Link Text [ ] URL [ ] Add Add a link, Add a bulleted list, Add a numbered list, Add a task list, Directly mention a user or team Reference an issue or pull request Add heading text Add bold text, Add italic text, Add a bulleted list, Add a numbered list, Add a task list, 1 reacted with thumbs up emoji 1 reacted with thumbs down emoji 1 reacted with laugh emoji 1 reacted with hooray emoji 1 reacted with confused emoji [?] 1 reacted with heart emoji 1 reacted with rocket emoji 1 reacted with eyes emoji Footer (c) 2022 GitHub, Inc. Footer navigation * Terms * Privacy * Security * Status * Docs * Contact GitHub * Pricing * API * Training * Blog * About You can't perform that action at this time. You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.