Archive for the ‘usability’ Category

Resizing content for the small screen

Wednesday, February 29th, 2012

Technical writers who produce both print documentation and online help know that you can’t just pour content from one format to another – the different media require different organizational techniques and writing styles. Now that we’re producing documentation for portable devices with small screens, we have to work even harder to make sure the content fits the device. Adobe’s Tech Comm Suite Evanagelist Blog has just published an excellent article by Maxwell Hoffman that explores this subject in more detail. It should be required reading for any writers who are producing online content.

When we read text on a handheld device, if the text is bulleted, indented, or formatted like a typical “technical” document, we can see the equivalent of about two or three spoken sentences. As soon as we “thumb down” to the next page, most of the visual context vanishes. We can only remember so much. This may be the reason that advertisement screenshots for eReaders universally display paragraphs from novels, not indented, bulleted text from technical communications.

Although a great deal of content from blogs and social media is pithy enough for handhelds, oceans of technical instructions destined for your smartphone screen are nowhere near ready to fit the confines of the small screen. If you are presenting steps or key points in a numbered or bulleted list, at a minimum, each item should be less than an iPhone screenful. If that bulleted “thought” or point straddles three or four Smartphone screens, reader retention will dramatically shrink.

I had an epiphany about this point recently when I found an online white paper I had authored about 5 years ago. My thumb nearly fell off scrolling through just three bulleted items. The content was effectively written and formatted for a “full” screen, but I didn’t have the patience for my own thoughts presented in the confines of a handheld smartphone.

Find your cursor with CursorAttention

Tuesday, January 31st, 2012

At work, I have a dual-monitor setup: a 19″ Dell monitor with a 4:3 aspect ratio in portrait mode and a 22″ Samsung widescreen monitor in landscape mode. I often lose the cursor when moving between monitors, generally when moving to the Samsung because it’s higher resolution and there’s a gap of a few inches between the monitors. Being nearsighted doesn’t help – even though I use a larger than normal cursor, I still lose it occasionally.

Last week I was watching a WebWorks ePublisher webinar and noticed something interesting – the cursor had a large yellow circle around it, which greatly increased its visibility. I queried the presenter, Ben Allums, and he pointed me to PenAttention (for tablets) and CursorAttention (for PCs). I immediately downloaded and installed CursorAttention and it’s made life much easier for me. You can adjust the colour of the circle (or a rectangle if you want that), its opacity, and size, and easily turn it on or off.  And it’s free.

I think it’s intended for people who are doing presentations, but it should word for anyone who has trouble locating the mouse cursor onscreen.

Thanks again to Ben Allums for pointing this out.

Filtering out retweets from Twitter searches

Thursday, January 19th, 2012

I use Twitter to follow several technical communication topics, including #techcomm and #framemaker. But I waste a lot of time scrolling though endless retweets.

Now I’ve found the solution to that problem – you can filter out retweets in searches by adding the -RT flag to the search. Thanks to LifeHacker for the solution.

Why the “Check Engine” light must be banned

Wednesday, January 18th, 2012

Here’s an article that focuses on usability, but in automobiles. In modern cars, why is there a “check engine” light instead of a more informative diagnostic display? Certainly the computers that run automobiles now can display more information about the state of your engine. It couldn’t possibly be because the manufacturers want you to go to their (overprices) dealers’ service departments? Could it?

I should note that with all the cars we’ve owned recently, the most common cause of the light coming on has been a gas tank cap that wasn’t on tight.

What’s not to like is that when something goes wrong, all the average motorist sees is that little drawing of an engine bisected by a lightning bolt. And all that tells them is basically nothing. The “check engine” light is the MIL (Malfunction Indicator Light) of the OBD-II system, and illuminates whenever a fault is detected. To see exactly what sort of fault takes a “special scanner” that plugs into the OBD-II connector. These scanners are almost always owned by mechanics or dealers. Independent people can buy scanners as well, or cables to connect laptops, smart phones, etc., but people who will do that are not the ones who need to worry about the check engine lights.

My mom, for example, is never going to be able to connect her laptop to the OBD-II connector somewhere under the dash in her Passat; it’s hard enough explaining to her how to connect a printer to her Mac. If her Passat just told her what codes were being thrown, she would at least have an idea about the condition of her car.

“We need a federal mandate that bans the generic ‘check engine’ light in new cars.”

But better yet — the state of things now is that your car actually could do more than just throw an error code at consumers. It contains an advanced system to diagnose itself, but the actual information from that diagnosis is not available to the car’s owner; the average owner must pay a dealer or mechanic to provide him or her with the codes, and what those codes mean. This is absurd. Early on, when in-dash displays were rare, one could understand why cars didn’t just display what codes were being thrown (though I think a little in-dash receipt-type printer would have been cool).

Google’s Android style guide

Friday, January 13th, 2012

One of the criticisms that’s been labelled at Google’s Android mobile operating system is that it isn’t as consistent and integrated as Apple’s IOS. To counter that, and to make life a little easier for developers (and eventually users), Google has introduced an Android style guide. As you might expect, it’s a very nicely laid out web site.

If you want to read more about it, Wired has an interview with lead Android developer, Matias Duarte.

Writing on the iPad – not!

Tuesday, December 13th, 2011

SF author Charlie Stross is a Mac fan and uses an iPad, but not to write on. In this post, he explains why, and discusses some of the shortcomings of the iPad interface when it comes to writing.

I think the answer is down to input methods. The iPad provides a couple of on-screen keyboards; but whoever designed them was aiming for simplicity, not generality. The missing Control key I can understand, for the same reason that the original Mac 128K had no arrow keys or function keys: it’s an attempt to block simple-minded ports of applications designed for the previous paradigm. What is less clear is why Apple omitted cursor movement keys from the on-screen keyboard. As it is, If you want to reposition the cursor you need to hold your finger on the text for long enough to trigger the magnifier and then drag the thing around using your finger, which is