Improve progress bar design
See original GitHub issueš Feature
Following on from #2656 I wanted to document the currently outstanding design improvements suggested by @jni, @tlambert03, @goanpeca and me. I donāt know if all of these suggestions should be implemented or whether theyāre the best options, so I think it would be good to get a design audit from @liaprins-czi before we go much further.
- Fix Vertical Jumping: as progress bars are added and closed, the displayed progress bars jump around to fill the available space. It would be nice to limit this and particularly for nested progress bars, reserve the rows of the child bars so that we donāt get the jumping around.
- Fix Horizontal Alignment: progress bars contract when the ETA is added, and donāt align depending on the size of the ETA label. The progress bar and ETA label should get fixed space to ensure they are aligned.
- Improve Scrolling Behaviour: the size of one scroll step is currently roughly equal to the height of a progress bar so there is a āstrobingā effect when scrolling. We should consider ways to avoid this.
- Remove Text Label: Having the word
activity
next to the expand/contract arrow is not the prettiest. We could consider having a greyed out version of the in-progress indicator as a clickable button for expanding and contracting, or perhaps some other more indicative icon. The concerns here are mainly around discoverability so it would be good to get @liaprins-cziās ideas on this - Auto-Close Dock: Consider automatically closing the activity dock when all the active progress bars have finished. Depending on the user workflow this could be pretty annoying as a new progress bar might start up pretty quickly after the last ones finished. Again, something @liaprins-czi should weigh in on imo.
- Move Progress Indicator to Own Thread: operations which block the main thread stop the progress indicator from moving smoothly and can be jarring. Having the indicator in its own thread could make for a much nicer experience.
I think Iāve covered all the current suggestions for improvement but of course any new suggestions would be welcome to make the progress bars as useful, discoverable and pretty as possible.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:3
- Comments:23 (23 by maintainers)
Top Results From Across the Web
Best Practices in Designing Awesome Progress Bars
And what to do to design awesome progress bars that boost user experience? Progress bars are visual indicators that inform users-. How long...
Read more >The UI/UX Design of Progress Indicator [Trends + Examples]
Improving the UX of Progress Indicators and Feedback Notifications ... Visibility of system status is one of the most important rules of UI/UX...
Read more >Using a Progress Bar (UI) in SaaS-Types and Examples
A progress bar (UI) is a tool to boost engagement and reduce friction in SaaS. Here's how you should use them, and how...
Read more >UX design patterns for Progress - Muzli - Design Inspiration
Tip: If the progress bar increasing at a steady pace, It will make people feel like things are slowing down. In a study...
Read more >How to manage user expectations with progress bars
A progress bar ensures the app is working and making progress. Good design will reduce user uncertainty, offer a reason to wait, and...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Based on last weekās community feedback, hereās the promised (tiny) prototype. If you click the button to collapse the pop up progress bars on the first page, the rest will progress on its own.
This is the combined UI elements discussed above in one image (the first image of the prototype):
This is what it looks like in the minimum window size napari has. Itās what I based the fixed size window on the other mock ups as well.
There are definitely more interactions to work through, but this should help give an idea as to how all the above decisions play together. As always, let me know what you think!
Some particular items Iām undecided on:
I love how this is shaping up! Great to be getting to consolidated feedback and decisions! š