3 ms·
As a user, I prefer short timeouts that pop up an error message with a 'retry' button. You need the retry button anyway, in case the server is throwing errors.
by tlb 6y ago
As a user, I prefer short timeouts that pop up an error message with a 'retry' button.
You need the retry button anyway, in case the server is throwing errors. And there's often no good place for a cancel button, without putting up a big 'Loading' animation.
- cortesoft 6y agoRetrying doesn’t help on a slow connection... if the best case connections speed of your user is slower than your timeout, you can retry infinite times and it wont help. Maybe increase the timeout on retry?
- nitrogen 6y agoExponential backoff but for the timeout instead of the interval, and/or a Wait Longer button, sound useful.
- iainmerrick 6y agoAs a user, I hate it when a program tells me I need to press “retry”! You’re the computer, you retry, and keep trying until I ask you to stop.
- pixl97 6y agoUntil it sits there and retires till hell freezes over and you don't realize anything is wrong. And that's the problem with timeouts, everyone has different expectations.
- asdfasgasdgasdg 6y agoIt's hard to go wrong by telling people what's happening and why. "it's taking longer than usual to X" is a fine thing to expose in a UI.
- iainmerrick 6y agoI should have stated my implicit assumption, that the program will tell me that it’s retrying. If I decide it’s not worthwhile I can stop it, sure. For any user-initiated action, automatic retry seems strictly better than failing on a single timeout.