4 ms·
The progress was meant to be truthful in both cases. Imagine the case in which someone is getting enough feedback from the backend to be able to show percent-wi
by _Microft 6y ago
The progress was meant to be truthful in both cases. Imagine the case in which someone is getting enough feedback from the backend to be able to show percent-wise changes vs. the case where updates are pretty coarse.
- matthewrobertso 6y agoI think the dishonesty comes in when the progress bar uses time as an input instead of observable events. It's fine and good to modify your api to return better progress information as long as that doesn't cause the operation to take longer or significantly increase load. However, representing a coarse process with time based progress is perhaps dishonest. For example assuming that step 2 of some 3 stage process always takes 20 seconds and artificially filling the progress bar over that duration is presenting potentially false progress to the user. For operations which may take a long time with some variance the user may be waiting for a while at a stopped progress bar and think an error has occured.