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

“Tea times” list UX feedback #761

Open
leothorp opened this issue Oct 29, 2018 · 0 comments
Open

“Tea times” list UX feedback #761

leothorp opened this issue Oct 29, 2018 · 0 comments

Comments

@leothorp
Copy link

I was looking at the tea times page, and noticing that it felt a bit confusing/difficult to navigate.. Currently there is a month-oriented way of viewing tea times- the user sees only the upcoming tee times for the current month, unless they scroll back to the top of the page and notice the “view for next month button”. at a glance, it can look like only the tea times for the current month are on the horizon for the foreseeable future. I'm wondering if the month is that relevant for somebody perusing the tea times (Should the fact that the month is ending in 2 days mean that they are not going to be shown a tea time that occurs in three days?) As a separate topic, it also feels like showing tea times in all cities at once presents some additional cognitive load for a user trying to find one to go to ( presumably, they would only be interested in viewing the tea times in one city at a time.) Wondering if it is worth considering a different way of organizing this information. One alternative that occurs to me would be a two-step flow- first, they are shown a screen that simply prompts them to choose a city. ( their selection here could be saved after the first time they go through this.) Then, they are taken to a page (with a dedicated URL for easy reference/sharing) that displays upcoming tea times for just that city. these would be paginated if necessary based on # of results (perhaps with something like infinite scrolling, which I'm familiar with implementing), rather than being paginated based on the month. Thoughts? happy to start chipping away at something like this gradually in the relatively near future if it sounds like a good direction to go in.

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

No branches or pull requests

1 participant