3 ms·
This seems like one of those things where the industry (and/or regulation) has stagnated and is missing really easy, obvious wins in UX. Why not beep at me or
by adrianmonk 7y ago
This seems like one of those things where the industry (and/or regulation) has stagnated and is missing really easy, obvious wins in UX.
Why not beep at me or otherwise alert me if it's night and I'm driving with my lights off? You know there's already a light sensor in the car, and there's already a way to beep at people or show them messages (oil is low, parking brake engaged, etc.)
There's a thing that beeps at me when my gas tank gets low. And there's a thing that beeps at me when my seat belt isn't fastened. So obviously it's OK to beep at me while driving. There's even a thing that beeps at me if I accidentally leave my headlights on and might drain the battery. Which is a fine thing to warn about, but surely not as important as a safety issue like driving with headlights off.
One could say that beeping at people whose headlights are off at night is not necessary because many cars (maybe most?) already have an automatic headlight mode, so the driver can just use that and the problem is solved. But that ignores one simple fact: people aren't doing it. Watch cars drive down a road at night, and it won't take long until you see someone whose headlights are off. I'd wager a lot of the time their car has an automatic headlight mode but they don't have the switch in the right position.
As computer people know from fighting server downtime, if something is important, you monitor whether it's behaving as required, and if it isn't, you alert.