Add a Comment (Go Up to OJB's Blog Page)
Entry 1893, on 2018-01-14 at 19:01:45 (Rating 3, Computers)
Nowadays, most people need to access information through computers, especially through web sites. Many people find the process involved with this quite challenging, and this isn't necessarily restricted to older people who aren't "digital natives", or to people with no interest in, or predisposition towards technology.
In fact, I have found that many young people find some web interfaces bizarre and unintuitive. For example, my daughter (in her early 20s) thinks Facebook is badly designed and often navigates using "random clicking". And I am a computer programmer with decades of experience but even I find some programs and some web sites completely devoid of any logical design, and I sometimes revert to the good old "random clicking" too!
For example, I received an email notification from Inland Revenue last week and was asked to look at a document on their web site. It should have taken 30 seconds but it took closer to 30 minutes and I only found the document using RC (random clicking).
Before I go further, let me describe RC. You might be presented with a web site or program/app interface and you want to do something. There might be no obvious way to get to where you want to go, or you might take the obvious route only to find it doesn't go where you expected. Or, of course, you might get random error message like "page not available" or "internal server error" or even the dreaded "this app has quit unexpectedly" or the blue screen of death or spinning activity wheel.
So to make progress it is necessary just to do some RC on different elements, even if they make no sense, until you find what you are looking for. Or in more extreme cases you might even need to "hack" the system by entering deliberately fake information, changing a URL, etc.
What's going on here? Surely the people involved with creating major web sites and widely used apps know what they are doing, don't they? After all, many of these are the creations of large corporations with virtually unlimited resources and budgets. Why are there so many problems?
Well, there are two explanations: first, that errors do happen occasionally, no matter how competent the organisation involved is, and because we use these major sites and apps so often we will tend to see the errors more often too; and second, large corporations create stuff through a highly bureaucratic and obscure process and consistency and attention to detail is difficult to attain under such a scheme.
When I encounter errors, especially on web sites, I like to keep a record of it by taking a screenshot. I keep this in a folder to make me feel better if I make an error on any of my own projects, because it reminds me that sites created by organisations with a hundred programmers and huge budgets often have more problems those created by a single programmer with no budget.
So here are some of the sites I currently have in my errors folder...
APN (couldn't complete your request due to an unexpected error - they're the worst type!)
Apple (oops! an error occurred - helpful)
Audible (we see you are going to x, would you rather go to x?)
Aurora (trying to get an aurora prediction, just got a "cannot connect to database")
BankLink (page not found, oh well I didn't really want to do my tax return anyway)
BBC (the world's most trusted news source, but not the most trusted site)
CNet (one of the leading computer news sources, until it fails)
DCC (local body sites can be useful - when they work)
Facebook (a diabolical nightmare of bad design, slowness, and bugginess)
Herald (NZ's major newspaper, but their site generates lots of errors)
InternetNZ (even Internet NZ has errors on their site)
IRD (Inland Revenue has a few good features, but their web site is terrible overall)
Medtech (yeah, good luck getting essential medical information from here)
Mercury (the messenger of the gods dropped his message)
Microsoft (I get errors here too many times to mention)
Fast Net (not so fast when it doesn't work)
Origin (not sure what the origin of this error was)
Porsche (great cars, web site not so great)
State Insurance (state, the obvious choice for a buggy web site)
Ticketmaster (I don't have permission for the section of the site needed to buy tickets)
TradeMe (NZ's equivalent of eBay is poorly designed and quite buggy)
Vodafone (another ISP with web site errors)
WordPress (the world's leading blogging platform, really?)
YesThereIsAGod (well if there is a god, he needs to hire better web designers)
Note that I also have a huge pile of errors generated by sites at my workplace. Also, I haven't even bothered storing examples of bad design, or of problems with apps.
As I said, there are two types of errors, and those caused by temporary outages are annoying but not disastrous. The much bigger problem is the sites and apps which are just inherently bad. The two most prominent examples are Facebook and Microsoft Word. Yes, those are probably the most widely used web site and most widely used app in the world. If they are so bad why are they so popular?
Well, popularity can mean two things: first, something is very widely used, even if it is not necessarily very well appreciated; and second, something which is well-liked by users and is utilised because people like it. So you could say tax or work is popular because almost everyone participates in them, but that drinking alcohol, or smoking dope, or sex, or eating burgers is popular because everyone likes them!
Facebook and Word are popular but most people think they could be made so much better. Also many people realise there are far better alternatives but they just cannot be used because of reasons not associated with quality. For example, people use Facebook because everyone else does, and if you want to interact with other people you all need to use the same site. And Word is widely used because that is what many workplaces demand, and many people aren't even aware there are alternatives.
The whole thing is a bit grim, isn't it? But there is one small thing I would suggest which could make things better: if you are a developer with a product which has a bad interface, and you can't be almost certain that you can improve it significantly, don't bother trying. People can get used to badly designed software, but coping with changes to an equally bad but different interface in a new version is annoying.
The classic example is how Microsoft has changed the interface between Office 2011 and Office 2016 (these are the Mac versions, but the same issue exists on Windows). The older version has a terrible, primitive user interface but after many years people have learned to cope with it. The newer version has an equally bad interface (maybe worse) and users have to re-learn it for no benefit at all.
So, Microsoft, please just stop trying. You have a captive audience for your horrible software so just leave it there. Bring out a new version so you can steal more money from the suckers who use it, but don't try to improve the user interface. Your users will thank you for it.
There are no comments for this entry.
You can leave comments about this entry using this form.
To add a comment: enter a name and email (both optional), type the number shown above, enter a comment, then click Add.
Note that you can leave the name blank if you want to remain anonymous.
Enter your email address to receive notifications of replies and updates to this entry.
The comment should appear immediately because the authorisation system is currently inactive.
Contact: OJB, OJB@mac.com. Features: Blog, RSS Feeds, Podcasts, Feedback, Log. Modified: 03 Mar 2007. Hits: 29,854,431.