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

Update summary/jump icon #6303

Open
alyblenkin opened this issue Aug 1, 2024 · 1 comment · May be fixed by #6516
Open

Update summary/jump icon #6303

alyblenkin opened this issue Aug 1, 2024 · 1 comment · May be fixed by #6516
Assignees
Labels
Milestone

Comments

@alyblenkin
Copy link
Collaborator

alyblenkin commented Aug 1, 2024

Blocked by #5420

We've heard feedback that the icon isn't intuitive.

We reviewed different options as a team, but landed on the classic list icon because it's the easiest to recognize, and hopefully won't need explanation.

  • Update east arrow icon with list icon .
  • We are still keeping the up icon when the user is drilling down into groups or repeats.
  • We will need to talk about this change in advance (maybe Insiders and a forum post).
@alyblenkin alyblenkin converted this from a draft issue Aug 1, 2024
@seadowg seadowg added this to the v2024.4 milestone Aug 6, 2024
@alyblenkin alyblenkin moved this from not ready to ready in ODK Collect Aug 12, 2024
@alyblenkin
Copy link
Collaborator Author

Adding this idea from a Collect fork here just for documentation.

It isn't well executed because it's thing and hard to see. I think the list icon is easier to understand, but this is still a nice concept to show a workflow or that you can jump from the summary view.
Image

@seadowg seadowg self-assigned this Dec 11, 2024
@seadowg seadowg moved this from ready to in progress in ODK Collect Dec 11, 2024
@seadowg seadowg linked a pull request Dec 11, 2024 that will close this issue
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: in progress
Development

Successfully merging a pull request may close this issue.

2 participants