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.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: