New user interface rule
Every action on a user interface shall result in a response from the computer in less than 0.25 seconds.
If the operation would take longer than 0.25 seconds to complete, the computer shall clearly indicate that it is processing, and not block the user from performing other tasks while the initial input is being processed.
This shall be guaranteed, no matter how busy the computer is, no matter if DNS or some other network service hasn't responded, no matter how much the disk drive is being thrashed, how little memory is available, whether you are compiling, or some other USB peripheral has decided to take a while to spin up a disk or generally hang.
The reason is because my biggest bug bear is devices not responding. The worst kind of hang is on a slow network. It drives me absolutely nuts that developers can't anticipate that maybe, just maybe, DNS or something else might get knocked out for a few minutes.
If the operation would take longer than 0.25 seconds to complete, the computer shall clearly indicate that it is processing, and not block the user from performing other tasks while the initial input is being processed.
This shall be guaranteed, no matter how busy the computer is, no matter if DNS or some other network service hasn't responded, no matter how much the disk drive is being thrashed, how little memory is available, whether you are compiling, or some other USB peripheral has decided to take a while to spin up a disk or generally hang.
The reason is because my biggest bug bear is devices not responding. The worst kind of hang is on a slow network. It drives me absolutely nuts that developers can't anticipate that maybe, just maybe, DNS or something else might get knocked out for a few minutes.
posted by Calum Grant at
9:10 pm
0 Comments:
Post a Comment
<< Home