Skip to content


Proving Your Identity—Smart Cards and the Sad State of the Art

I am in the process of updating my vCard to the new 4.0 standard, and decided it was time to once again obtain a digital certificate that I could use to sign and/or encrypt e-mail messages with. And since I have a laptop with a Smart Card reader, I figure it would be great to leverage it for more secure logins, file encryption, and a few other things. The only digital certificate that can do all those things is the ITU’s x.509 public key infrastructure (PKI) standard, which dates from 1988.

There are many reasons why the average person, not just this geek’s geek, would want to do this:

  • Sign important documents digitally, without having to FAX them (first patented in 1848, with the modern standard first published by the ITU in 1988, coincidentally)
  • Encrypt sensitive work-related e-mail
  • Make secure payments on-line and in-person, avoiding the inherent insecurity of a standard credit card
  • Providing a more reliable method for logging in to web sites (so that we mere mortals with imperfect memories don’t have to choose between insecure and hard-to-remember passwords)

But there is no off-the-shelf way for me to easily and quickly obtain and use such a certificate. Oh, I can do it, and will do it, but doing so will mean navigating an unpleasant labyrinth without a decent map.

So why, after nearly a quarter-century after this standard was first published, is PKI so hard and confusing to use a decade into the 21st century? There is no one answer, but there are several whose confluence shows us a path forward.

  1. Because it’s really, really, really hard.
  2. The standard was developed by computer engineers and mathematicians who don’t think like the rest of us.
  3. It was developed far before the modern age of design thinking and research that has taught us how to design technology that is easier to use.
  4. Because Steve Jobs didn’t seem to care about it.

Number 1 is an understatement, to say the least. Reading the above Wikipedia article will give you just a taste of the problems, and the topic of my next post. The most fundamental difficulty is the difficulty in defining what an individual is in a way that a computer can understand, but that another individual cannot duplicate.

Number 2 is best exemplified by this quote from the Wikipedia article on X.509:

“The X.509 specification suffers from being over-functional and underspecified and the normative information is spread across many documents from different standardization bodies.”

Solving number 3 may or may not be possible with X.509. I’ll explore this issue in a future post.

I present number 4 with my tongue only partly in my cheek. So many of the best-designed things have been created or led by one person with a strong passion and vision for creating elegant things. In this case, not one of the major technology companies, nor any individual public figure in technology has made it their mission to create a scheme that was both secure and easy enough to be used by the average person.

Posted in Standards, Web.

Tagged with , .


Starbucks’ In-Store Wi-Fi Experience

There is a contagious misconception among those retailers that offer Wi-Fi to patrons.

The belief is that the Wi-Fi splash screen should bombard visitors with a wide variety of content that is (mostly) irrelevant to the customer experience.

Wrong. If I’m using the Internet at Starbucks, for example, you can be assured that surfing Yahoo is not at the top of my list.

It would be much better to limit the content to things that are unique to the business, keep their number limited, appearance simple, and their exclusivity strongly highlighted.

Starbucks is not horrible, but it still suffers from being too busy, from weak messaging, and from missing anything really cool.

Starbucks Wi-Fi Splash Page

The top bar is actually a pretty good start. But I would replace the Foursquare check-in with a similar Facebook check-in. Spice it up a little by including unique store details in the default text. Something like duplicating the store amenities listed in the iPhone app would be great.

There are a few other things that should be done prominently to enhance the customer experience. Fill that empty space in the header up with the store amenity icons from the iPhone app, and when I click on it, show me all the details–store hours, and the menu.

An easy link to the store would be nice. I’m looking at a particular mug, and want to look up its details and reviews before I buy it. Gaining easy access to this will increase the odds of me buying it right now. (And just to be clear, no, it’s not the Michael Bublé song!)

Next, ditch anything I can get for free surfing the web. Since much of the WSJ content is behind a paywall, make sure you always show and link to ~3 features that require payment when not using Starbucks’ Wi-Fi, and make it obvious to the visitor what value they are getting.

Make room to show the current drink and food specials available. A picture of the yummy gingerbread loaf just might make me hungry enough to buy a slice.

I love the iTunes Pick of the Week download; and that should be kept. And it’s so much easier and more automatic than having to pick up one of the paper cards, remember that you have it, and then type in the redemption code. Frankly, I’m not sure I would have bought the music I’m currently listening to without discovering it on the list of past picks, but I’m enjoying it thoroughly, and will surely buy an album or tTherewo because of it.

That’s a good start, but to finish we need to back up to the sign-in page.

There should be two ways to log in.

  1. Via a simplified version of the existing screen, that only takes up the right half of the screen. Yes, you can keep making people read all the legalese in this one.
  2. A much prettier, very simple log-in that uses my Starbucks Reward Card account, and gently tells me I’ll be able to access additional things I can’t get with the other log-in. Like maybe that’s what it takes to get the free access to the WSJ. And cache the log-in so I don’t have to enter it every single time I visit.

Once you do that, then you can offer me a customized portal page that reminds me what my Rewards balance is, what music I’ve bought through Starbucks, and begin to offer some more social content.

Make me feel wanted and special, please. Use this to build a relationship with me, instead of feeding me content whose benefit to you is some revenue-sharing agreement with Yahoo, the WSJ, or ESPN.

Just my 2¢

Michael Steven Bublé

Posted in Marketing, Wi-Fi Hotspots.


Starbucks App Critique, Part 3—Drink Builder

What I think should be the coolest feature of the Starbucks App is the most frustrating for me, and I’m guessing is also the least-used part of the program.

Starbucks Drink Builder

It starts off extremely well, with two simple choices (HOT or COLD) and an equally awesome pair of images that makes the selection even easier. Then it devolves into a long boring list of text choices.

The drink I’m trying to add this morning is a good example of how confusing and tedious the app is to use—a venti Peppermint Mocha with soy milk. How many taps, and how much time do you think it should take to create this favorite?

First off, I don’t see categories for mochas or lattes. Yes, mochas and lates are listed under the category of Espresso on the Starbucks menu boards, but how many people realize that these two drinks are just variations of espresso, or are within eyesight of a Starbucks menu board when they want to create a favorite drink?

Drink categories list

I looked under Classic Espresso, and didn’t find it. Ditto with Signature Espresso. And neither had a choice that was anything like “Custom”, “Seasonal”, or even just a plain mocha or late as a starting point. The presence of classic and signature categories is just silly; customers don’t care or remember whether a drink is in one of these categories.

Solution: Make the categories under Espresso be something like Espresso (with Cappuccinos and Macchiatos), Lattes, Cappuccinos, and Mochoas. The first or second item in all should a basic drink that can be customized, as in “Custom Latte” and “Custom Mocha”.

So I find the only mocha drink on the Signature Espresso page (White Chocolate Mocha) and start customizing it. I select the size, check the number of shots, change the milk to soy, tap the white chocolate syrup down to zero (5 taps alone), tap the peppermint syrup once to set it to 5, set the toppings to chocolate curls, select preparation, where I select Double Cup, and am then perplexed at “Ristretto”, “Upside Down”, and “With Room”. There is no way to look up what any of these options mean. “With Room” should at least say “With Room for Milk”.

Syrup customization

Next is add-ins. Nearly all of these are self-explanatory, but why is soy milk separated from 1% and 2% milk? And why are there any milks here when I already had that choice in a previous tab? Confusing the user like this is bad; it increases the odds that he or she will give up and quit, or wind up with a drink that isn’t quite what they want.

Finally, after 5 minutes and 42 taps, I have my Peppermint Mocha, which is labeled “Venti Pepermint No White Chocolate Soy…” (and then Peppermint Mocha in much smaller text). Because I had to customize a different drink, this name is more complicated than it needs to be, making recognition on my list more difficult. And the last important detail in my custom drink is not really customized; the app warns me that the nutritional information may not be customized for my changes.

This is too complex and hard, and the results are less-than-stellar (pun intended).

Final Peppermint Mocha drink

On my second attempt, I noticed Caffè Latte in the Classic Espresso category (is this the most basic kind of latte?; the app shouldn’t leave me wondering about questions like this). Starting with this drink resulted in an easier process of creating my custom drink, because I generally didn’t have to remove items (save for deleting the whipped cream and replacing it with peppermint whipped cream, which I finally noticed on the list, albeit below the fold).

I haven’t even commented on the “My Friends’ Drinks” or “Scanner” features yet.

Normally, I don’t like to end an article on a sour note, but the problems and solutions are deep and complex enough that it will require a few days of geeky research and ruminating to come up with improvements that are worth sharing.

But for now, I will just say that the custom drink aspect of the Starbucks App should be its most prominent and used feature, and there are several ways in which it can be enhanced to drastically increase customer engagement and loyalty.

Posted in Design, iPhone, Usability.


Starbucks App Critique, Part 2

Spending a little bit more quality time with the Starbucks App, I find other aspects of even more frustrating than those I mentioned in the previous post.

The first problem I had is part bug and part UI copy. I tried to refill my card via a Visa, and the app asked me for my password. So I tried the password I thought I had set up for the app, and it was rejected. So were all of the other variations I thought I might have used. Oh! Since it didn’t say to enter the app password, maybe it meant I should enter my PIN and use it as a debit card. Nope; that didn’t work either.

My next thought was to log out and log back in again, but I avoided doing that for several minutes because I was afraid I had truly forgotten my password, and would have to go through a cumbersome reset process on the phone. But when I overcame that bit of fear the app instilled in me, I logged in on the first try, and that’s all it took–the app did not ask me for my password again when processing the payment.

Solutions: Check the code that asks for the app password, and find the bug. Then insert the word “app” before “password” in the payment security check dialog box, so that no user could think that you are really asking for the CC PIN.

The second problem can be fixed with the streamlining of the help/FAQ text, an additional button on the home screen, and some slight changes to the Rewards page.

I can reasonably assume that the app was designed by people who are expert users of the Starbucks Reward Card, including all the benefits its holders are entitled to. So they never give a second thought to the lack of readily accessible information on the card’s use and benefits.

Addressing this issue is of course important to improve the customer’s experience using the app, but it is also fundamentally a marketing issue. In this 15 MB of the app, the benefits of the card are relegated to a page that takes at least 5 taps to reach (assuming you’re on the home screen and know exactly where it is), and read more like vague leagelese than happy marketing copy.

The rewards benefits should be made crystal clear, should relate to the current status of the card (welcome, green, or gold), and be consistent with the reward card brochures that are sometimes displayed in the stores. Most importantly, doing this right will improve the customer experience in a way that management might not have realized. It doesn’t matter how good your employees are, or how well you train them; there are always details they will forget because they don’t deal with them every day. Being able to tap once in the app and show the barista what benefits I’m entitled to will remove confusion between them and I, and avoid the frustration that I had the third time I tried to use my card.

Me: “Does the reward card include free refills on tea?”

Barista: “No, just more hot water.”

So I ordered coffee, which I did not enjoy as much as I would have enjoyed two cups of tea.

Reward Card Brochure: “One free additional tea bag” (which I read later)

Solution: Ditch the full image of a reward card on the My Cards page, and use the extra space to include the current reward level, number of points needed to the next level, and a very short list of the benefits accrued, with a button that says “Details” the user can tap to read a one-page screen that has all the important details (and/or show it to the barista). That can then link to the existing copy on the Rewards screen.

The third problem is the drink configurator, and really deserves its own post.

Posted in Design, iPhone, Usability.


Starbucks Complicates iPhone App

I love coffee. I love my favorite Starbucks even more. A nice comfy leather couch with an AC outlet 6″ away, almost-decent Wi-Fi, an oven to heat up lots of delicious things, and one of the amazing but still-rare Clover Brewing System machines.

But I’m disappointed by the Starbucks iPhone app, and I’d like to give their developers some advice on improving it.

First, why are their two similar apps in the iTunes store? Both apps include a GPS-enhanced store locator and an electronic version of your Starbucks reward card, complete with a barcode that makes it fast to pay with (and get free refills!).

The “Starbucks Card Mobile” app came first, and its description even explicitly states users should download the “single app” instead. Leaving the older app in the store confuses users about which one to download, especially since the release date is newer (Nov 9, 2011) than the supposedly enhanced Starbucks “single app”  (July 15, 2011).

In many ways, this is the superior app. It is simple, easy-to-use, and includes only features that nearly every single user will use. It is a well-designed effort to make customers happy and hooked, which is the key to loyalty.

The Starbucks app adds the ability to send eGift cards via email or Facebook, to save custom drinks (more on this in a separate post), view food and coffee menus, a barcode scanner (bereft of any instructions about what to scan and why) and browse Starbucks job opportunities. And oh yeah, a prominent, can’t-be-deleted link to SDN—the Starbucks Digital Network. And it is more than three times larger, topping in at nearly 15 MB.

And it is missing icons for the iTunes Wi-Fi store and Clover coffee in the list display of nearby stores, making it very difficult to quickly find the closest place to get my Clover fix. (Yes, you can specify a filter for it, but that takes more time and taps than just showing all the amenities icons.)

What percentage of Starbucks’ customers do you think are interested in a job with the company? Some for sure, but few enough that this feature simply clutters and complicates the app for 99% of the users. This should go.

I am sure that Starbucks hopes to increase revenue by driving people to its Yahoo-partnered portal, but I suspect that even fewer customers are interested in this than are interested in working for Starbucks. Yahoo’s sites are invariably cluttered and lacking the attractiveness and enjoyability of most any Web 2.0 site. Continuing this association with Yahoo hurts Starbucks’ brand, in my opinion. It also is simply a link to a web site, and thus takes you out of the Starbucks app. This is not a good user experience.

Brew a Better App

First, the navigation bar at the bottom is a great feature, because there are a few things one will always want to be just a tap away. But it should not scroll, because there aren’t more than 4 of these things:

  • Kill the SDN and Jobs icons.
  • Kill the Help icon and replace it with a small information symbol (a circled roman serif i) in a corner of the app.
  • Consider making the Settings icon a small icon in a corner of the screen, as well.
  • Move the  Rewards and eGifts icons to the main screen.
  • Fix the Food icon—crossed utensils may look cool, but anything that looks like an X should only be used for the concept of “cancel”, period. This lesson was learned many decades ago during the design of wayfinding symbols for airports. And it would be much better to simply use the same icon for food or snacks as the AIA symbol set uses.
  • Please make the coffee bean icons look a little less like a pair of lips about to kiss.
  • Leave the home, My Card, and Stores icons in the navigation bar.
  • Move the myDrinks icon to the 4th slot in the navigation bar.

Next, bring over the missing icons from the Starbucks Card Mobile app, so that users don’t have to filter the search results just to see which amenities nearby stores have what they desire.

There are also a few symbols that are ambiguous or inconsistent with existing symbol conventions that should be redesigned.

Look at the app screens above, and see if you can figure out what each icon means without using this glossary. Several of them are good or very good, because they follow existing conventions and are thus obvious.

But a few are difficult to associate with their supposed meaning. This leads me to the hunch that Starbucks had graphic designers make these icons, without the benefit of any help from symbol design experts, and without properly testing them with potential users.

The Wireless Hotspot needs no explanation, because nearly every device that has Wi-Fi uses that exact icon. Same thing with the Drive-Through car icon; the correct association is fairly obvious (though a front-profile of a car would suggest parking, and should be avoided). The beamed eighth-notes for an iTunes Wi-Fi music store is good, but would be even better if it used the exact same shape as does the iTunes application, with the circle around it.

The clock for “open now” is less obvious, but still a ready association, which is strengthened by its grouping with the word “open” in actual use.

The stylized clover is ideal, because it is exactly the same shape as is used on the Clover Brewing System machine, and is unique enough to be recognizable. The Starbucks Reserve icon, while the same as used on the packaging, is idiosyncratic to me; I don’t make any association between its design and the concept of “reserve”. Frankly though, I don’t have a suggestion for improvement. I can only surmise that for those who have become hooked on the reserve coffees, the association for them as is strong as is my association with the Clover icon.

The two symbols that need the most work are the Mobile Payment and Oven-warmed food icons.

First, the open flame icon is not the best association with food warming. It might be appropriate for Burger King, which uses open flames to grill its burgers, but nothing about it makes the association with the ovens that Starbucks uses. I don’t want my scones to be scorched by a flame!

Actually, it wouldn’t really be appropriate for Burger King either, because it too closely resembles the open flame used in fire-safety symbols and signs. It is bad to associate any symbol used for safety issues with something benign, because it lessens the impact of the symbol when seen on signs related to safety. (The symbols for prohibition and do not enter are often abused as well; they should not be used for such things as cancel and delete in computer software!)

A better choice would be the international standard symbol for heat, (space-permitting) enclosed inside a simple line drawing of an oven. These three wavy arrows are used universally on all kinds of things that radiate heat, including car defrosters, heated leather seats, and even on the bottom of oven-safe containers.

Designing an improved mobile payment icon is a bit more difficult to design. One problem with the existing symbol is the space between the motion bars and the dollar sign is not much less than that between adjacent symbols. It might be enough to move the two closer together, and perhaps even slant the dollar sign, to emphasize the concept of speedy payments.

A new symbol should not look anything like the Tap & Go logo used on near-field communications terminals (and on compatible credit cards, cell phones, etc.), because it uses a barcode shown on your smart phone screen instead of RF.

A simplified 2D barcode with the dollar sign might be better. Or surrounding the dollar sign with a simplified 2D barcode. A dollar sign inside a simplified smart phone screen would be ideal, but I don’t think the available pixels are enough for such an icon to be recognizable.

And of course, these changes should be tested according to the ISO guidelines. (e.g. you need to ask test subjects what they think each symbol means, without providing any hints. Multiple choice questions, as I’ve seen used, produce bad and misleading results.)

Posted in Design, iPhone, Usability.


How not to Design a Library Book-Return Robot

I’m a geek, and I love technology—especially anything that automates boring, repetitive tasks. So I should be a huge fan of the barcode-scanner wielding, German-engineered book-return robot that the Foster City library installed a few years ago.

Nein.

It’s way too slow, confusing, and unreliable.

Signage and Instructions

The most visible telltale of any poorly designed object or user interface is when it starts sprouting after-the-fact documentation.

For instance, there are tons of laminated letter-sized paper signs taped up at the Millbrae BART/Caltrain station, directing you where to go for particular trains. What? The expensive fixed and programmable signs designed into the station weren’t enough? Bad architect—no vino!

In the case of these robots, there are three additional laminated paper signs (and the most important are now fading—I would have hoped the librarians knew of UV-proof ink) on each of the machines. The etched-in text on the stainless steel and the programmable 19-inch color touchscreen weren’t enough? Bad designer—no martini!

Make the Right Customer Happy

The more egregious problem is that the library management who selected the technology vendor apparently thinks that the customer they were serving was the library staff.

Wrong. The customer they need to make happy is the library patron. Automating the sorting for the library staff is a nice secondary benefit. It’s an important benefit, but one that cannot be realized unless you solve the primary task of getting the patrons to use the fancy machine.

To accomplish this, the solution needs to have these properties:

  • Be easy to use
  • Be reliable
  • Be fast
  • Be better than the old method

But the extra signage shows these book robots are not easy to use. And while barcodes have been used in grocery stores for many decades, with an exceedingly low mis-scan rate, these machines are able to recognize barely one in ten of the books I present to them.

The requirement to scan books one-by-one combined with the high reject rate results in a system that is neither reliable nor fast.

And that combination makes it frustrating for the patron and worse than the old method. The only advantage for the patron is that if he or she puts up with these problems, they can get a return receipt when the library is closed.

The old method is still superior in all regards, for the patron at least.

  • I can drop a stack of books on the librarian’s desk, and ask for a return receipt.
  • The librarian might complain and point me to the machine outside, but will grudgingly give up and scan the books and issue the receipt—faster and with fewer errors than the machine.
  • Even with the complaining and pointing, the process is faster than using the machine. And doing it inside is much nicer, too.

Nothing about the new process is better than the old one, except for the after-hours return receipt.

And because the typical library patron response to this is to give up on the machine and use the manual book drop or pester the librarian, it’s not really better for the library staff, either.

Why Did This Fail?

The question of why is easy to answer. The library management viewed their customer as their staff, not their patrons.

The how is more interesting. Without having been involved in the selection, installation, and check-out, I can only base my conclusions based on external observation, my knowledge of barcode scanners, and a little bit of testing (on the order of 15 minutes worth).

During the installation, I was a frequent visitor to the library. The installation and check-out took far longer than the library had stated. From my vantage point, watching the Germans tweak the installation over the course of a month or two, it seemed likely to me that there were very few of these systems in existence, and that the library likely purchased a system that was still in development, or was built by a company that’s just not quite competent enough.

The components of this process barcode scanning, conveyor belts, and computer-driven sorting) are such old and established technologies that it should have been easy to find a ocmpany already expert at this.

Given these observations, I naturally expected that the fundamental problems with scanning resulted from politics and bad communication between the vendor and the library staff, and the acceptance process being different than real-world conditions.

You see, the barcode label for every book is protected by a layer of plastic. A shiny, glare-reflecting dust jacket on hardcover books, and a self-laminating covering on softcover books.

Acting on a hunch that the old-fashioned laser barcode scanners were having difficulty with the reflective covering over the barcodes, I roughed up the covering over several book barcodes with a ceramic nail file. But there was no improvement.

Perplexed, I decided to generate and print my own replacement barcode for one book. The library uses CODABAR—an old, simple code created by Pitney-Bowes. A few minutes on a barcode-generating webiste, and I was off to the library to test my theory.

But I fared only marginally better than with the real book, so something else was obviously wrong.

The Right Perspective Reveals All

Given the nature of how the books need to be held up to the outside scanner (the right side of the above picture), I had assumed the unit contained a modern multi-axis laser barcode scanner. These are standard issue at checkout stands across the globe, and use spinning mirrors or holograms to project a bird’s-nest of scan lines across the target area, to ensure quick reliable scanning, no matter the orientation of the object being scanned.

But that’s not what these book robot engineers used.

They used an old-fashioned, single-line scanner. One that requires the barcode to be placed precisely under the projected scanline. The scanline the library patron can’t see because the book is between the scanner and his eyes. (Thank God for that, since it is a laser!)

As soon as I discovered this, and held my books at an angle matching the scanner head, and made sure the laser line covered the barcode, my scan success rate and speed jumped up to what you’d expect from a grocery checkout line of 30 years ago.

The Problem Lies Deeper

But that’s just the first scanner.

Once you scan the book to open the magic door and place the book on the conveyor belt, there is a second barcode scanner that attempts to find the code.

Again, my success rate is miserable, and I resort to using the manual book drop. Again, there is an old-style single laser line scanner tucked inside.

If you feed more than one book at a time, and the first book is rejected, the machine chides you for not following the rules, and spits them all back out at you. Not nice.

This is not rocket science, it’s barcode scanning!

The solution is fairly straightforward. Rip out the linear laser barcode scanners, and replace them with multi-axis laser or image-based scanners, and test the system against a good cross-section of library materials before accepting (and paying for) the fixes from the vendor.

Oh, and hire new executive staff for the library. Preferably people who have run profitable businesses, instead of government bureaucracies/cost-centers.

Posted in Barcodes, Design, Usability.


The Disappearing Clue

This morning’s software frustration: I entered an address into Google, and it popped up a text bubble that asked if I wanted to share my location, along with a “tell me more” link. Clicking on that link dismissed the text bubble, so that when I returned the question was gone, and along with it the clue of where to click. (Not that it mattered, because

Bad UX designer, no Twinkie!

Posted in Design, Usability.


Smart Phone, Dumb Software

I’ve got my iPhone out, and the Starbucks app loading, ready to “pay” for my refill, when the phone rings.

A true smartphone wouldn’t hide this app completely, and then make me relaunch it after I hung up.

Fortunately, there was nobody in line behind me.

Posted in Design, iPhone, Usability.


Universal Remote ≠ Easy Remote

I spent some time this afternoon helping a retired and widowed neighbor install a new set-top box and reprogram her universal remote.

There were several things about this process that troubled me.

The first is that the telephone company doesn’t send their service technicians out into the field with replacement boxes. This results in a delay while the replacement unit is drop-shipped. And it also results in either a second service call, or the customer leaning on a neighbor to do the install. (Will this problem disappear once all retired people are Gen-X or younger?)

The second is since the newer box is smaller than the older box, the company’s instructions to ship the old set-top box back in the cardboard box the new unit came in are geometrically impossible.

The third is the universal remote.

I will admit that this particular remote is a better solution than my neighbor juggling five remotes (TV, stereo, set-top box, DVD player, VCR player). When it works, it works beautifully.

But it suffers from two problems:

  1. The uni-directional nature of the consumer IR remote protocol.
  2. The confusing UI on the remote.

I obviously can not fault Logitech for problem 1. But for problem 2 to exist at all on a device with that big of a color screen is sad.

Whatever sequence of events causes the remote to get out of sync with the devices happens often enough that my poor neighbor must frequently use the “repair programming” feature of the remote. And I say poor neighbor because the wizard-like procedure confuses even this seasoned geek. I can’t fathom the frustration she feels.

All of the unit’s prompts to repair/resync its programming are plain-text, without any pictures, or even a reminder of what type of device each is. The wording was precise, but still confusing. Just a little bit more context of what and why it’s doing each step would help greatly. As in, “I think I just turned on your TV, stereo, and cable box, and turned off your DVD player and VCR; can you please confirm this as I ask you the state of each device?” (But with fewer words!)

And a simple icon of a TV, DVD, VHS tape, etc. would be a great way to reinforce which device you should be looking at when the remote asks you if it’s on or off. A picture specific to each model that shows you how to tell would be even better. (Would you believe there are at least three different colors used to indicate “ON” among these 5 devices?)

A universal remote should work so seamlessly that it all but becomes invisible (and it should work in the dark, without you having to look down at it). There is room for something magical in this space, but Logitech clearly hasn’t yet found the right spell. Nor is the Apple TV remote even attempting to be in this space, but I can’t help but wonder how amazing a full Apple TV will be. Will it solve the problem of universal remotes? Will it even need to?

Posted in Design, Remote Controls, Usability.

Tagged with , , .


A Little Hazy on iCloud Setup

The holy grail and cardinal rule for making computer software easy to use is to never leave the user confused. Apple is generally the best at this, but we Windows users sometimes feel like the black sheep of the family when it comes to usability. This problem that I encountered today is also typical of turning the verbose dial down too far.

I am simply trying to begin using iCloud with my existing Apple ID, following the instructions on Apple’s site verbatim. But those instructions and this alert box are missing something important. How the devil do I get an iCloud account? I think I know what the problem is–I bet you have to create one on an iOS 5 device–which I don’t yet have.

Leaving out important information such as this may allow the designer to rejoice in the simplicity of the UI they created, but it confuses the user. The addition of just a few more words would eliminate much confusion. Never assume the user knows the fundamental reason behind your error message. The simple addition of “You can create an iCloud account only on iPhone, iPad, or iPod Touch devices running iOS 5.” would instantly set users on the right path, one devoid of all confusion save for “why?”.

Posted in Design.

Tagged with , .



oem downloadable software download oem autodesk autocad vertu replica mobile