{"id":199,"date":"2010-03-28T17:23:12","date_gmt":"2010-03-29T00:23:12","guid":{"rendered":"http:\/\/kai.mactane.org\/blog\/?p=199"},"modified":"2011-08-10T13:08:49","modified_gmt":"2011-08-10T20:08:49","slug":"how-failtastic-can-one-phone-be-just-ask-palm-about-the-pr","status":"publish","type":"post","link":"https:\/\/kagan.mactane.org\/blog\/2010\/03\/28\/how-failtastic-can-one-phone-be-just-ask-palm-about-the-pr\/","title":{"rendered":"How Failtastic Can One Phone Be? Just Ask Palm About the Pr\u0113!"},"content":{"rendered":"<p>Here are a few things that I consider to be basic requirements for functionality in a smartphone, along with notes on how my Palm Pr&#275; fails to deliver:\n<\/p>\n<dl>\n<dt>When I press the power switch, the phone should turn on.<\/dt>\n<dd>(Assuming the battery is charged, of course. And I&#8217;m willing to accept that a modern smartphone needs to be charged every night. No problem there.) But given that, when I press the &#8220;on&#8221; switch, I should see the screen light up within, say, one second. It should not take ten seconds. By the time ten seconds go by, I&#8217;ll assume that I must not have pressed the power switch hard enough, and I&#8217;ll try pressing it a second time.<\/p>\n<p>        Did you know that the Palm Pr&#275; stores power-switch presses in its input buffer? That means that when the phone finally <em>does<\/em> get around to waking up, it processes the first impulse, lights up the screen&#8230; and then immediately blanks it again as it processes the second impulse. This is extremely frustrating.<\/dd>\n<dt>When the screen lights up and shows me an &#8220;unlock&#8221; icon, it should actually let me unlock the unit.<\/dt>\n<dd>I&#8217;m not complaining about the fact that it shows me that icon. I recognize that it&#8217;s there to conserve my battery life by making me prove that I&#8217;m a human being, and not an inanimate object that jostled the phone in a crowded purse or backpack. I&#8217;m fine with that.<\/p>\n<p>        What I&#8217;m <em>not<\/em> fine with is having to try three-to-five times to get the icon to recognize my input. And it&#8217;s not like the Pr&#275; stores <em>this<\/em> stimulus in its input buffer, so if I just wait for it to catch up&#8230; it blanks out the screen and I have to try again.<\/dd>\n<p>        <!--more--><\/p>\n<dt>When a call comes in, I should be able to answer it.<\/dt>\n<dd>I&#8217;ve lost track of how many incoming calls I&#8217;ve missed because I couldn&#8217;t get the phone to turn on in time to catch the call before it went to voice-mail. The screen was showing me the name and photo of the friend who was calling me&nbsp;&mdash; sometimes a friend who I&#8217;d explicitly asked to call me, and whose call I was anticipating&nbsp;&mdash; and yet <em>I couldn&#8217;t actually pick up the phone<\/em> and say hello to them.<\/p>\n<p>        This is what we in the user interface biz call a <strong>total, ignominious failure<\/strong>.<\/p>\n<p>        (Most of the time, the failure is because the damned &#8220;unlock&#8221; icon wasn&#8217;t taking input yet, so this is really just a special case of the problem above &#8212; but it happens in such a different context, and it has such different consequences, that it counts as a separate item.)<\/dd>\n<dt>When I type on the keyboard, the characters should show up within 5 seconds of the keypresses.<\/dt>\n<dd>This has the benefit of allowing me to realize that the keypresses have triggered, as well as letting me see what the hell I&#8217;ve already succeeded in inputting. It lets me see if I need to go back and fix a typo. It gives me that warm, fuzzy feeling that the phone might actually respond to my input, instead of just sitting there imitating a sleek, shiny, black, sexy rock.<\/p>\n<p>        Waiting a full <em>ten seconds<\/em> (as has happened to me on occasion) is even worse. I wouldn&#8217;t want you to get the impression that 5 seconds is the worst delay I&#8217;ve ever seen on the Pr&#275;; it&#8217;s just the limit of what I&#8217;ll accept as &#8220;basic minimum functionality&#8221; (and I think even that is being incredibly generous).<\/dd>\n<\/dl>\n<p>At least once per day, the Palm Pr&#275; fails me on at least one of these completely basic requirements. When it works, it&#8217;s kind of nice, and even manages to be useful some of the time. But there are just too many occasions when it flat-out <strong>fails to function<\/strong>. I&#8217;m sick and tired of being out on the town with friends and having someone say, &#8220;Can we look up such-and-so on Yelp?&#8221; and then struggling with my phone for five minutes before giving up and saying, &#8220;No. I can&#8217;t look that up for you&#8221;. At which point some kind soul with a <em>working<\/em> smartphone takes pity on me and finishes the job in about a minute.\n<\/p>\n<p>This is also not meant to be an exhaustive list of the Palm Pr&#275;&#8217;s failings, or those of webOS. There are all sorts of UI and UX decisions I could rail against, but I don&#8217;t want this blog to become a full-time anti-Pr&#275; and anti-webOS blog. I have wider interests than that. This post is just meant to be a list of the <strong>basic, core usability failures<\/strong> that have driven me to distraction.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Here are a few things that I consider to be basic requirements for functionality in a smartphone, along with notes on how my Palm Pr&#275; fails to deliver: When I press the power switch, the phone should turn on. (Assuming the battery is charged, of course. And I&#8217;m willing to accept that a modern smartphone [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[39,56,57,29,10,30],"_links":{"self":[{"href":"https:\/\/kagan.mactane.org\/blog\/wp-json\/wp\/v2\/posts\/199"}],"collection":[{"href":"https:\/\/kagan.mactane.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/kagan.mactane.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/kagan.mactane.org\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/kagan.mactane.org\/blog\/wp-json\/wp\/v2\/comments?post=199"}],"version-history":[{"count":5,"href":"https:\/\/kagan.mactane.org\/blog\/wp-json\/wp\/v2\/posts\/199\/revisions"}],"predecessor-version":[{"id":384,"href":"https:\/\/kagan.mactane.org\/blog\/wp-json\/wp\/v2\/posts\/199\/revisions\/384"}],"wp:attachment":[{"href":"https:\/\/kagan.mactane.org\/blog\/wp-json\/wp\/v2\/media?parent=199"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/kagan.mactane.org\/blog\/wp-json\/wp\/v2\/categories?post=199"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/kagan.mactane.org\/blog\/wp-json\/wp\/v2\/tags?post=199"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}