| Bram Cohen ( @ 2005-09-17 21:57:00 |
Configuration Proximity
One thing which has irritated me for a long time about configuration of software programs is that the configuration UI is always nowhere near the thing it's configuring. Users waste a huge amount of time trying to figure out where the configuration UI is, and what in it corresponds to what they want to configure. If there were simply a 'configure this' button which was always visible and always took you to the right configuration option, everything would be much better.
Speaking of bad UI, it irritates me no end that smoke detectors signal low battery via a chirping. It's a superquick high-pitched noise, seemingly designed to provide as little audio location information as possible while maximizing the likelihood that it will wake you up repeatedly in the night every night from the time the batteries get low until the time they become completely dead because you couldn't find the thing. Smoke detectors have built-in lights, why can't they start flashing the light when the batteries get low? That would add no extra battery drain, and make it easy to find the smoke detector with low batteries.
To that end, why can't Motorola cell phones be programmed to either not chirp when their batteries are low, or at least not do it between 10pm and 10am? Why are these devices so important that they need to wake me up to attend to them at 3am? As a general rule, if end users want to smash something repeatedly with a sledgehammer, that's a sign of bad UI.
One thing which has irritated me for a long time about configuration of software programs is that the configuration UI is always nowhere near the thing it's configuring. Users waste a huge amount of time trying to figure out where the configuration UI is, and what in it corresponds to what they want to configure. If there were simply a 'configure this' button which was always visible and always took you to the right configuration option, everything would be much better.
Speaking of bad UI, it irritates me no end that smoke detectors signal low battery via a chirping. It's a superquick high-pitched noise, seemingly designed to provide as little audio location information as possible while maximizing the likelihood that it will wake you up repeatedly in the night every night from the time the batteries get low until the time they become completely dead because you couldn't find the thing. Smoke detectors have built-in lights, why can't they start flashing the light when the batteries get low? That would add no extra battery drain, and make it easy to find the smoke detector with low batteries.
To that end, why can't Motorola cell phones be programmed to either not chirp when their batteries are low, or at least not do it between 10pm and 10am? Why are these devices so important that they need to wake me up to attend to them at 3am? As a general rule, if end users want to smash something repeatedly with a sledgehammer, that's a sign of bad UI.