So, I am in a situation where I am developing an internal application that executes a list of many task items, some of which have multiple steps. For each task item, I also have a progress bar.
Well, considering how fast these steps happen, some progress bars literally jumps from
Now, my 'bright' idea was to slow down the background job ever so slightly that the user can see a smoother animation of the progress, but not so much that the job takes significantly longer.
Is this an acceptable practice? Or is this something that is used in commercial applications? Is it advisable to do this (or not to)?
I am intending to slow down the background job by just putting the thread to sleep for maybe... 50 milliseconds at a time.
At this point, it doesn't make sense to change my progress feedback UI, which I know might avoid this issue altogether. So, for the purpose of this question, assume that each task has a progress bar associated with it.
What do you UX experts think about slowing down the job for a smoother animation?
This is a very similar question, but I don't think it seems to address my question fully.
The answer by Aadaam is what I was thinking about doing. I am wondering if this practice is acceptable (not how to implement it). Though if there is a particular way that implementing makes it acceptable, please share!
As I re-read my question, it seems as if I'm talking about any type of application. Perhaps I should clarify that:
- The job (as a whole) could potentially take as much as 15+ minutes.
- It is important to me that the users know exactly what is happening. The information that is displayed is useful to the user, not solely the developer.
Here is an example of the type of UI I'm working with: