predictability is a crucial part of the user experience

I put the phone in keyguard mode. I put the phone in my pocket. The phone wakes up the first person in my address book at 6am. This has happened more than once, and I ended up creating an address book entry named “aaaaaaaa”. My husband did the same with his phone. The problem: key guards can get turned off, sometimes in the pocket and sometimes by sequences of events.

I put the phone on silent, turning the ringer volume all the way down. I close the phone. My husband calls and interrupts the meeting with a loud ringer. The problem: when I closed the phone, the software canceled the action. I was supposed to wait until the screen returned to idle state. I made this error for over a year before figuring out the timing component.

This is on two different phones, both of which are reasonably easy to use. But both have caused me profound professional embarrassment. They cause me to have to turn off the phone. This is not in anybody’s best interest: not the device manufacturer, not the operator, not content providers.

Always on is a key value for the mobile. Let’s fix this.

Leave a Reply

*
To prove you're a person (not a spam script), type the security word shown in the picture.
Anti-Spam Image