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

Search results count needs to be more useful for food-seekers #2216

Open
8 tasks
fancyham opened this issue Sep 17, 2024 · 0 comments
Open
8 tasks

Search results count needs to be more useful for food-seekers #2216

fancyham opened this issue Sep 17, 2024 · 0 comments
Labels
Feature: Search Search tool for Food-seekers Role: Design UI/UX User interface / user experience design Role: Front-end Front End Developer

Comments

@fancyham
Copy link
Collaborator

fancyham commented Sep 17, 2024

Overview

What did you observe or what is a likely problem?

Right now, our search results say "604 results" which, while accurate in that that's the total number of matching results... while that's a nice bragging point for us, that's not a very useful number for food-seekers in their immediate task because it's not relevant to their current search (because they're unlikely to travel across LA to access a pantry on the other side of the county) for nearby food.

image

What is the user trying to do?

The user is probably trying to find nearby pantries. So if we show, say, the nearest 20-30 to the searched address, that should be more than enough. While it's possible a food-seeker might look at the 31st, but they'd probably want to explicitly expand their search area, or better, they'd probably simply move the location they're searching on.

How many people are / will be having this problem?

Currently, everyone on desktop.

Discussion and possible Solution(s)

What device is this happening on / what is the user’s context?

Currently this only occurs on the Desktop -- the tablet portrait and mobile modes don't show total # of search results.

Since desktop has more space, we could perhaps show better information.

Something like "30 nearest locations (out of 604 total results)" when searching on a point address

Or, if searching for a region:

"30 nearest locations (there are [X] locations within "[RegionName]")

If we can add pages, that would also help users. For example: Page 1 shows locations 1-10, page 2 shows 21-30, etc.

Discussion and possible Solution(s)

Possible challenges, solutions?

Resources/Instructions

How do others solve this?

  • Look at other web-based map websites like Yelp, Google, etc.

Things to think about?
What pieces of information are most useful for the user on this screen?

Action items

  • Discuss with Research and other designers, PMs, etc. what information is needed up there?
  • Mock up alternatives for the results.
  • Should there be pages of results? On what screen sizes? (desktop only?) If pages, does that change the text? ("showing 1-10 of 604 results, sorted by distance").
  • Create designs and specifications with logic for devs
  • Devs create beta
  • Test it and revise
  • Once it's good, launch

Also, consider a staged approach -- changing it little by little on the public site might be fine as long as devs are willing to make quick changes like that.

@fancyham fancyham added Role: Design UI/UX User interface / user experience design Role: Front-end Front End Developer Feature: Search Search tool for Food-seekers labels Sep 17, 2024
@fancyham fancyham changed the title Search results count isn't precise enough Search results count needs to be more useful for food-seekers Sep 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature: Search Search tool for Food-seekers Role: Design UI/UX User interface / user experience design Role: Front-end Front End Developer
Projects
Status: Prioritized Backlog
Development

No branches or pull requests

1 participant