1-Button Simplicity: Not Really...

“One button operation!” Well, that’s a neat little marketing phrase which probably tests well with focus groups, who think it’ll be easy to use, right? Not when that one button is supposed to control quite a few different functions on a device whose whole identity is based on convenience! Check it out:

Turning On & Off: When the thing’s off, press it “3-5 seconds or until the blue light flashes” to turn it on. First of all, this actually does vary within that 3-to-5-second range – strange, since more precise timing is definitely achievable on such a device. Even stranger, it varies outside that range, in a way that seems to depend on how recently the headset had been on – if I haven’t used it for a few days, it could take 9 seconds; if it was on a few hours ago, only 2. Ugh. But now, ignore exactly how long it has to be pressed, and think about the feedback it gives to the user. I’m turning this thing on when I’m driving (heh heh, guilty), so I have to hold the headset up in front of me, keeping an eye on it to catch that split-second flash to confirm that I’ve done the job. And if I miss the flash, good luck – holding it another second or two puts it into pairing mode, which is a whole different hell.

Status: So, is it on or off? The whole preceding diatribe isn’t even the beginning when you’re not sure if the headset is already on or not. If it’s on, the only clue it gives is an occasional and very brief flash. You’ve got to keep your eye on the darn thing for some time to know its status, and that’s not only annoying, it’s inconvenient. A fast-paced mobile user who’s interested in convenience (sooo, exactly the kind of person who wants a Bluetooth headset in the first place?) wants status instantly and clearly. Not accomplished here!

Calling: Here’s a fun one. Holding that one button, while the headset is already on (see above to get there), for the correct amount of time will call “the last person you called.” So let me get this straight – I’m in my car, the headset is on (at least I think so), I want to call the little lady, I put my finger on that button.... and I have to pause and think... think, think... was she the last person I called? Did I call her with the headset or just the phone? (And does that even matter?) More often than not, I just bust out the handset and hold “2” to speed dial her. Motorola, why can’t that single headset button be linked to a speed dial number, if it’s going to have a calling function? (Voice dial is even better, but support for that feature apparently varies by both phone AND service provider, thanks a lot, cell companies.) The bottom line: convenience in this case is supposed to be about removing unnecessary actions and unnecessary thought from the process. This one-button wonder drops the ball on the latter.

Accidental Calling: This is a theme I address repeatedly in mobile phones: I don’t want to be able to accidentally call someone, change a setting, power on or off, or anything unpredictable from my pocket. I don’t want a single exposed button that does any of those things when pressed long enough, because in a pocket, that’s just too possible! And the single-button headset is a violator in just about every way. It can power itself on (see above) and make a call (see above again) without its user being any the wiser, if it just gets squeezed in the right way – although since those are things I can’t muster intentionally, my pocket would have to be pretty damn tech-savvy...

Ending a Call: I can’t seem to get this right. Holding the button for some amount of time hangs up, but for another amount of time puts the caller on hold. How many times have I left a message one someone’s voicemail that lasted an additional 10 minutes when I unwittingly put’em on hold? I guess I’ll never know...


So what’s the truly convenient alternative to the one-button approach? Simply put, more buttons. I was so frustrated with the one-button model I originally had that I switched to the boom-microphone model – that little swinging mic is the on/off switch. You know when it’s on, when it’s off, and how to switch it, no question about it. My gripes about calling, accidental calling, and ending a call still apply, but one step at a time, right? Design is iterative, and Motorola is getting there. Unless someone else puts some real thought into it and beats them to the punch...