3 ms·
> We were calling their API, and the app was clearly just waiting for results, which sometimes would take half a minute. Clearly to whom? You shouldn’t expect
by Someone 3y ago
> We were calling their API, and the app was clearly just waiting for results, which sometimes would take half a minute.
Clearly to whom? You shouldn’t expect your users to know that your client’s API may be slow.
> I added a progress bar that started at 5% went +10% every second till 65%
That’s bad. If you don’t have a reasonable estimate for how long something will take, you should use an indeterminate progress bar.
https://m2.material.io/components/progress-indicators#usage https://m2.material.io/components/progress-indicators#usage:
“Determinate and indeterminate
Progress indicators may be determinate or indeterminate:
Determinate indicators
Determinate indicators display how long a process will take. They should be used when the process completion rate can be detected.
Indeterminate indicators
Indeterminate indicators express an unspecified amount of wait time. They should be used when progress isn’t detectable, or if it’s not necessary to indicate how long an activity will take.”
For this case, I would wait a second or so to see whether an answer returns rapidly, then pop up an indeterminate progress bar and keep it up for at least a second, even if the reply comes sooner.
- raverbashing 3y agoFor real If you think your client will wait 30s without any visual feedback of what's being done you need to study about UX. This is one of the reasons why tech people "I'll just write an app" fall flat on their attempts. UX matters, a lot
- ksaj 3y agoThe Raspberry Pi OS Install (and some other Linux installs) simply change the image on the screen detailing various features or whatever. You may or may not see them all. You may or may not see them repeat. But what you do see, is that the system hasn't crashed and is still doing something. So a fake progress meter isn't really necessary.