Journal Journal: human interface design: alarm clocks
Why does using a standard $20 WalMart alarm clock remind programmers of toggling data into a PDP-4 one bit at at time? Because that's what they're doing. So why do alarm clocks still have one-bit user interfaces after all these years? And why do they have an array of buttons on top, which you're likely to hit while fumbling half asleep?
Why do alarm clock programmers often have doubts about what the state of the clock is? Eg: after you hit snooze 10 times, will you keep getting your alarm? 30 times? There's no indication on the front panel that says what the state is. Classic user interface problem: hte user doesn't know the state because it's not shown.
And why do most alarm clocks have that damn sliding switch that breaks after N cycles. They know you'll use that switch twice a day every work day.
The original alarm clock chips from National and Intersil and so on had lines for each button and slide switch. They designed the interface. In the 1970s. They wanted to minimize the number of switches and wires to connect to them because those things are labor intensive and even then they had profit margins. Everyone keeps using the same basic chip interface or even the same chips, just putting a fancier plastic case on the same electronics. Good for them, economy of scale.
Okay, so that's where the inscrutible user interface came from. So why don't we get a new one after 30 years?
What would a well designed alarm clock interface look like? Voice recognition?
me: "Clock, get me up for my Smith appointment."
clock: "Okay."
clock: "Wake up time. Wake up time. It's seven."
me: "Gimme another hour."
clock: "Your appointment is for eight. You have to get up now."