Tag: usability

Posted on
by

If you’ve been following the Firefox 4 betas, you’ve probably noticed that they’re dumping the status bar. OK, a lot of people didn’t use it, but here’s the thing:

When you hover over a link, the status bar tells you where it will take you.

This is important (especially for security) — important enough that they’ve moved the functionality elsewhere…but in a broken manner. They’ve put it into the location bar — you know, the field where you type in a URL, or look to see where you are.

The problem is that there isn’t room in the location bar to show the full URL of a hovered link except for very short links. The status bar has the entire width of the browser. The location bar has to share that space with the navigation buttons, the search box, the feedback button (during the beta), any custom toolbar buttons, the site name on secure websites, etc.

Just about every link I hover over ends up with critical information cut off in the “…” between the start of the hostname and the parameters at the end. That’s almost useless. (Almost, because at least the hostname is visibla, but it would help to see the page name as well.)

Displaying the target URL in some way is core functionality for a web browser, and you shouldn’t remove or break core functionality. In some ways this is worse than the proposal a few years ago to remove “View Source,” because that at least isn’t core functionality for a browser (though it is core functionality for the web, because it encourages people to explore and tinker and learn how to make their own websites — which is exactly why that was put back in). It’s crazy that I need to install an add-on to get back something as basic as a working preview for links.

Posted on
by

I suppose I can understand putting one of those “If this is an emergency, please hang up and call 911” messages on a health insurance phone menu. But if you’re going to have one, shouldn’t you put it before the five-minute member identification/sign-in process, not after?

Admittedly, the process only took that long because their voice recognition system wasn’t getting along with my voice, but still, isn’t the point to route people to the fastest response in an emergency?

Posted on
by

Serious stuff (news, usability, history, etc.):

And not so serious:

  • Fantastic image: Firefly crew as the Enterprise crew. Classic Star Trek, of course. One thing that really struck me was the reminder that there’s really only one woman among the regular classic Trek cast: Uhura. Nurse Chapel and Yeoman Rand are there, but neither of them would really have had the kind of focus that Kaylee, Zoe, Inara and River have here.
  • Incredible custom action figure maker Sillof collaborated with Glorbes on a Star Wars in World War II series.
  • The webcomic SMBC presents: The Logogeneplex! I’m pretty sure I’ve read stuff that this was used on. (Warning: archives are NSFW.)

Posted on
by

It was fast. Anticlimactic, really. It took a few reloads to get the Comic-Con International home page up, but once I could click on the reservation link, everything went smoothly. I was done by 9:05.

The reservation page was actually optimized!

  • Just one image: a banner across the top.
  • Everything was on one page, including the list of hotels, the personal info, and the hotel choices.
  • Hotel selection was done by client-side scripting, so there was no wait for processing between selections (and no risk of typos confusing their processing system later today).

This is a huge deal, especially compared to Travel Planners’ horribly overdesigned 2008 forms — yes, forms, plural — that kept bogging down. (I never even saw last year’s, though I tried for an hour and a half to get in.)

On the downside, that one page does load a half-dozen script files, but that doesn’t seem to have slowed it down much.

In case none of your 12 choices were available, they asked for a maximum price you’d be willing to pay for another hotel that’s not on your list. I vaguely recall this being a feature of the old fax forms, but I don’t remember being asked this on the phone last year.

I was surprised to find that they didn’t want credit card info immediately, but that’s good from a streamlining perspective as well. The hotel choices, room type, and contact info are critical in order to make the reservation in the first place. Payment can be done later, so in a rushed situation like this, it’s better to handle it later. Plus, not asking for credit card information means that they could run the site without encryption, speeding things up a bit more.

I would have liked to have gotten a confirmation number for the request, or an email, just so that I could be sure that I was in their queue. And to be sure that I entered the right email address. And the right start and end dates. And…well, you get the idea. I’m a little paranoid about the process at the moment.

Here’s hoping that the back end of the process, and sending out confirmations, goes as smoothly as the front end did.

Update: Short answer: it didn’t. Long answer: I’ve written up what went wrong, at least from the guests’ point of view.

Posted on
by

San Diego hotel rooms for Comic-Con International go on sale tomorrow morning at 9:00 AM Pacific Time. Because they’ve sold out in a matter of hours the last few years — or, more precisely, because they’ve overwhelmed the reservation system while doing so — Travel Planners is instituting some new policies and a new procedure.

Last December they announced that they would require a deposit at reservation time, and a cut-off point in May after which it would no longer be refundable. This should help cut down on some of the “just in case” speculating that always happens. (Previously you had to provide a credit card when making the reservation, but they didn’t charge it.)

As for the procedure, here’s what used to happen: You would search for hotels, get a list of those that have rooms available, enter your name and contact info, then enter your credit card and get immediate confirmation. At every step, the server would be slow, and there was a good chance that you would have to start over. Yes, it would even fail at the last step.

The new scheme is wildly different: Instead of searching for a hotel, you’ll be asked to enter a list of up to 12 choices, in order of preference, and submit it. A few hours later, they’ll send you an email to confirm what you’ve gotten.

My first thought: this is exactly how it worked for me last year, when I got through on the phone instead of online. It’s also how reservations by fax used to work.

It’s annoying not to have instant feedback of course, but I suspect one of the main reasons the system breaks down is that it’s trying to handle so many complete transactions simultaneously. This way, the only part running “live” is collecting requests. Once those are all in, they can process them at whatever speed the reservation system can actually handle.

Plus, if they really want to minimize the load on their website, they can put everything on one page and minimize the number of graphics and scripts. Every image you have to load slows the page down. Every new page you have to load is another chance for the process to break down completely. When designing a web application, there are times to emphasize looks, there are times to emphasize convenience for the user, and there are times to emphasize simplicity in the actual process. This is one of the latter.

I guess we’ll see how it goes tomorrow morning.

Update: The request process, at least, went surprisingly smoothly. ← I’ve got some thoughts here on the reservation form and how the process worked.