-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Empty states in search results #5834
Comments
@alyblenkin this would be a good one to look at! |
@dbemke this is a good point! We don't want them to see the empty state when they are using the search. ideas:1. Search results feedback
3. Showing similar/best results to avoid dead-end
4. Proactive search 5. Option to also filter results @seadowg let me know what you think! |
All good ideas! I think I'd definitely want to go with the smallest change here for the moment - adding a specific message for "no results". |
@seadowg I'll mock something up to discuss next week. |
I think "search 3" is a winner as well! Could you update the issue description with that? |
Updated Dec 20
Solution
We want to display a relevant message for the search results and make it visually different from the empty states.
Figma link
Copy:
"No results
Try another search"
UI:
ODK Collect version
after merging #5768 (and other empty states PRs)
Android version
10, 13
Device used
Redmi 9T, Galaxy A23
Problem description
The text in empty states is shown not only when there are no forms on the list but also when a user looks for (via search) a form that is not on list.
In previous versions of empty states in some parts of the app the text was "Nothing to display” and also with some more text in other parts (examples in screenshots below).
Example: User looks for a form that is not on the list in "Start new form" and gets information: No blank forms. Download form to get started.
Steps to reproduce the problem
Examples:
Or
Expected result
Maybe it would be possible to introduce a separate text for empty search results?
The text was updated successfully, but these errors were encountered: