90 percent of everything : Usability Blog
Written by Harry Brignull

Archive for October, 2006

By “Unlimited” we, er, mean, limited. Very limited.

October 26th, 2006 by Harry Brignull3 comments

Misleading advertising?

I’m surprised to see the way ISPs and telcos still describe their products so misleadingly, even after the trouble that Talk-talk got into with the ASA about offering free broadband “Forever”. Orange are currently running a campaign that uses the word unlimited broadband in the same breath as “talk” and “texts”. If you go to the website you’ll find that talk is in fact very limited – either limited to just landline calls or just off-peak, on-network mobile calls.

It’s not a good idea to draw people in with false promises. Why do it? It upsets your potential customers just as they are coming in the door for the first time, and makes you look untrustworthy. A few months ago I signed up to a Three mobile contract with their “mobileWeb” add-on. It turns out, they actually meant “mobileWalledGarden”, i.e. you could only access a small set of specially selected sites. I took the handset back and axed the contract. No more Three for me, for now.

Notes from ‘Death of the Desktop’ talk by Aza Raskin

October 26th, 2006 by Harry BrignullAdd a comment

Death of the Desktop by Aza Raskin

Even reading the bullet points was pretty illuminating. Imagine what the talk was like! (on second thoughts – give me the bullet points every time. It’s like reading the Cliff Notes instead of the book which reminds me of the last time I was pretending I’d read Milton).

Aza Raskin is the son of Jef Raskin so if stuff like that runs in the family, probably should be listened to.

Damn. Lost a long post.

October 25th, 2006 by Harry Brignull3 comments

I was in the middle of a remarkly erudite post on the art of filenaming (honest) when Firefox decided my cursor wasn’t in the text edit box. My continued typing involved a backspace which of course took me off the page. Bang. Post gone.

Makes you realise that running apps in browsers sometimes takes away the safety nets you’ve got used to. I used to be rather careful on this front and would always type stuff into notepad before instead of straight into a browser. Much safer.

Do you know what made me become careless?

Damn GMail and it’s auto-save. It’s never lost an email and therefore I’ve started getting cosy about typing into text fields again. And thus I get shafted by Wordpress. I’m off to see if there is a plug-in for it that does auto-save :-(

Interfaces for Power Users

October 24th, 2006 by Harry Brignull2 comments

In Productivity and Screen Size,  Jacob Nielson trashes a recent Apple survey on how fabulous large monitors are for productivity. (He doesn’t actually say he disagree’s with Apple’s results, just that their methodology was suspect).

I’m not quite sure whether the rest of the article has much to do with monitor sizes but he does say some interesting things about designing interfaces for casual users as as opposed to skilled users. He argues that very different constraints apply when you design for one group other another and furthermore there are fewer situations when you can assume your users will have time to become skilled in your interface than you would assume.

So even when you think you are designing a tool for people that will have the time and incentive to become familiar with your innovative, optimised design then there are many times when the user will be starting from scratch.

An example for me is Photoshop. Now Photoshop is such a huge program that there are many areas I rarely need to use. When I do use them, quite often that part of the interface has been revised since the version of Photoshop I was using when I last went there. So despite using Photoshop pretty much every day for something or the other, there are times when I am a newbie. I like to hone my skills so I will try and learn something new in these situations but in many cases the clock is ticking and I just have to get results quickly.

Everyone is both a power-user and a newbie at different times. The cases where a tool or a piece of software can guarantee it will only be used by power-users or people learning to become power-users is fairly uncommon.

So ideally software should have lead you gently in but get the hell out of the way for people who already know what they are doing. Context senstive help, wizards, tooltips and interfaces that have ways of hiding advanced features*  all help in this.

* howver hiding/changing parts of the interface to simplify things for new users can also hinder the ability to discover new features by exploring the screen as well as negating the benefits of motor memory. (i would describe motor memory in this context as the process where you learn to quickly move to the correct button/icon/control by habit much quicker than you would be able to locate it by conscious action)

The inevitability of cruft

October 24th, 2006 by Harry Brignull1 comment

ITworld.com – The inevitability of cruft

So you learn from that experience and decide that the next thing you design will be cruft-proof. So instead you slam right into the Second-system Syndome

It’s tricky making stuff. That’s why 90 percent of everything is crud. ;-)

Shopping baskets shouldn’t expire

October 21st, 2006 by Harry Brignull2 comments

Twice in the last few days I’ve spent some time choosing some online purchases and then got distracted or had real life intervene.

I’ve left that browser window open and when I come back to it the next day I have attempted to complete the purchases only to find that the shopping cart has expired. Is there a security risk here that I can’t see that makes it necessary to have a time-out on shopping carts? I can’t think of one. I haven’t entered any personal details at this point and if someone else used my computer and discovers that I was about to purchase 400g of Jack Links’s Peppered Beef Jerky and some inkjet cartridges then I can withstand the shame and embarrassment.

So I may or may not get around to making those purchases now. I may go to a different supplier or I may decide that I don’t need that much beef jerky. That’s a lost purchase that is down to a programming decision that may not have even been made consciously. The coder may have used used a default without really thinking about it. I bet it wasn’t discussed by management at any point…