Skip to content
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

Improved user guidance through surface quest #76

Closed
claudiush opened this issue Apr 1, 2017 · 6 comments
Closed

Improved user guidance through surface quest #76

claudiush opened this issue Apr 1, 2017 · 6 comments

Comments

@claudiush
Copy link

As a first time user of StreetComplete I found the road surface quest to be a bit hard to understand. I think the quest flow can benefit from a few interaction improvements to guide the user through the flow:

  1. After having tapped on the first surface option ("Paved (generic)") the screen should switch to the full screen surface selector view to clarify that the next step is to pick the right subcategory (or just confirm the changes via "OK" at the end of the form). Currently user still needs to scroll down to open the full selector screen
  2. After a top surface category (Paved / Unpaved / Ground) has been selected the other categories should be visually tuned out. I suggest applying a black and white filter and decreasing the opacity.
  3. After the top surface category has been selected a call to action text should be added to clarify that as a next step the user should pick the subcategory. E.g. "...now select the most fitting subcategory:"
  4. After the subcategory has been selected there should be some hint that to complete the quest the user needs to scroll down and hit "OK". I would suggest that the form should scroll all the way down to show the "OK" button.

The following is a mock of suggestions 2 and 3:
streetcomplete_quest_guidance_mockup

@westnordost
Copy link
Member

Currently user still needs to scroll down to open the full selector screen

Actually, I tried to implement scrolling down to make the expanded elements visible but failed. Don't know how to. :-(

  1. & 3.

Hm I don't know, this is a matter of taste in my opinion.

This will be a generic problem for any such quests whose answer selection takes up the whole screen space and more. So I think this should be solved generically for any quest. I thought about perhaps making the buttons at the bottom floating the scrolling area, OK invisible as long as nothing has been input yet. However, this is something for later versions.

@waldyrious
Copy link
Contributor

How about using a paging feature, like a sideshow, or one of those installers with next/previous buttons?

In fact, using this approach we don't even need to have all the options visible at once, and thus avoid scrolling altogether :)

Here's how it could work: We could have the three main options as small squares side by side, which would fit in the bottom part of the screen, without scrolling; then, when one main option is selected, the page would slide left to give way to the sub-options page, and throughout this process there could be either prev/next links below the images (with the "next" link turning into "finish" or "ok" at the end) or alternatively, small arrows at the left and right borders of the pages (with the right arrow turning into a checkmark at the end).

What do you guys think?

@westnordost
Copy link
Member

Ah, iOS style. Well, it is also a valid choice to select one of the "categories". If the view slides into the subpage right away, how can I then just "unpaved"?

@waldyrious
Copy link
Contributor

Maybe one of the sub-options could be "Other" or "Generic"?

@HolgerJeromin
Copy link
Contributor

You could try to put the OK button to the top...

@westnordost
Copy link
Member

Oh yeah, that would work@waldyrious

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants