September at paulcarvill.com, the home of Paul Carvill on the web 2009 at paulcarvill.com, the home of Paul Carvill on the web

link: paulcarvill at flickr

paulcarvill.com

Hi, I'm Paul Carvill and I'm a web developer. I am Head of Interface Development at LBi, Europe's largest digital agency.

I also like walking, cooking, Bollywood and rock 'n' roll.

Archive for September, 2009

Wallpaper* Open House map is a prime example of awful Flash interface design

Saturday, September 19th, 2009

Further to my previous post regarding the Adobe-Omniture deal, and how it might improve the consistently awful Flash user experience people regularly have to deal with, this morning I found a very good example of bad Flash interface design to illustrate my point with.

The weekend of 19th and 20th September is London Open House weekend, when the public gets wide and varied access to the architectural pleasures of the City. Unfortunately, while Open House do publish a printed programme, the only way to discover locations of Open House participants online is through a fairly complex and ugly search form at http://www.londonopenhouse.org/public/london/find/. This method is not an intuitive way to find Open House locations, and does not encourage discovery or serendipity.

However, there is a map at Wallpaper magazine’s website. While this could have been a useful alternative to the official listings, it is instead problematic and discouraging. The Wallpaper site features a Google map, overlaid with a Flash map. There are several problems:

  • The Wallpaper Flash map features only a selection of the full listings. They call this the Wallpaper Edit. For the full listing you must still consult the printed programme or use the official search form.
  • The Wallpaper Flash map is extremely simplified, and lacks context, scale and travel information, as well as several other navigation aids.
  • The Wallpaper Flash map uses an entirely new and different navigation method. There is no drag control, and no zoom. Instead, the user needs to click on buttons near the top of the map which signify arbitrary areas of London. There is no option to show partial areas or the whole map at once.
  • The Wallpaper Flash map uses an entirely different scale to the accompanying standard image-based Google map. Changes in the orientation of one map are not reflected in the other, making switching between the two extremely disorienting.
  • The Wallpaper Flash map uses bespoke markers and a bespoke popup system, which opens a popup at the top left of the map, completely out of context of the click event. The Google map operates in an expected way, much as other web standards-based online maps do, by opening the popup at the location of the click event, where the user is focused.

The frustrating thing about Wallpaper using a custom Flash interface is that the Google map view already provides all the functionality the user needs, in an established, expected way, and in many ways in offers a superior user experience. Control of the Google map is more granular and direct, and the user benefits from the extra context and transport directions functionality. In addition, in case of the popup, the Google map provides more information, in the form of opening times. Even simple things, like the detail text being copyable, make the Google map a far more suitable implementation.

The Wallpaper Open House Flash map interface is a perfect example of the continued redundancy of Flash interface design, it’s ability to encourage design abuse, the lack of understanding of user behavioural patterns and the skewed importance of brand over usability.

links for 2009-09-18

Friday, September 18th, 2009

The Flash user experience is regularly awful

Friday, September 18th, 2009

If the Adobe-Omniture deal means anything it’s that with feedback from behaviour tracking Flash developers might finally get around to addressing their applications’ regularly awful user experience.

Designers of Flash apps and widgets seem to go back to the drawing board every single time they make something. They start from scratch each time, creating new and confusing user interfaces to reflect whatever the fashionable paradigm of the time is — whizzy, futuristic dashboard? No problem! Over-elaborate transitions? Easy-peasy! Flash intro on your splash page? No sooner said than done (but is it still 1999?).

The problem with this approach is that with each new app and its innovative bespoke interface, users are regularly forced to learn a new method of navigation. The web has well-established, native patterns of interaction that do everything you need them to. Discoverability, when implemented correctly, is a finely nuanced mechanism for delivering complex systems to the user. But Flash apps are too often clunky, unnavigable, hastily put together bits of software designed to capitalise on trend and satisfy business interests keen on some thing ‘jazzy’ or ‘funky’. Way back in 2000 Jakob Nielsen said that Flash was 99% bad, Flash encouraged design abuse, and made bad design more likely, and not much has changed since he made those statements.

Flash applications avoid many established design patterns, are often explicitly designed to be impermanent, and regularly lack fallback content in the instance of the correct plugin not being installed, but these issues are rarely considered by a business pushing for a snazzy new feature they can parade before their board.

Hopefully the Adobe-Omniture deal will set off a new era of closely-monitored stats which might prove useful in finding where Flash applications and interfaces could be improved, and where using web standards to build a long-term solution might prove a more fruitful endeavour. Of course, Flash analytics can currently be recorded by other analytics tools such as Google Analytics, but Omniture is a far bigger hitter on large scale websites, and where influential Flash design is needed the most in order for good practice to trickle down into common usage.

links for 2009-09-16

Wednesday, September 16th, 2009
  • A beautiful video of everyday Sydney, Australia life. "This is a personal project that will document 12 months of life in 'Little Sydney'. I'll be releasing films every month or so in short film format and conclude the project with a piece that brings together the highlights." It uses the tiltshift effect to make everything look like a miniature version of itself.

links for 2009-09-15

Tuesday, September 15th, 2009

A collection of HTML5 links, documents and discussions

Tuesday, September 15th, 2009

The movements around discussing, designing and implementing HTML5 are gaining real momentum now, and it was definitely one of the big buzzwords at the summer web conferences this year. I’ve started implementing one or two small pieces of the spec on production sites, and am looking forward to using some of the long-awaited functionality like the form-validation work that’s in there, as well as the offline storage that’s already been relatively widely deployed (well, by Google, at least: Cache pattern for offline HTML5 web applications). So I’ve been monitoring the specification documents a little more closely than usual, as one of the important things about working in some of the more developmental areas is knowing that the spec is likely to change.

As part of that, I’ve rounded up here some of the recent linkage around the HTML5 spec:

Zeldman
Zeldman, publisher of A List Apart, founder of Happy Cog Studios and “King of Web Standards” (according to Business Week), approves of the direction HTML5 is taking, although he does have a few issues with the spec. But, he says, “…many things we had previously considered serious problems were fixable issues related to language.”

“Half of standards making is minutia; the other half is politics.”

http://www.zeldman.com/2009/08/31/loving-html5/

HTML5 Super Friends
Zeldman’s friends like the direction of HTML5 too, and are happy to publicly say so, as part of the HTML5 Super Friends group:
http://www.zeldman.com/superfriends/

Although some people have griped that it would have been more conformant to use the proper channels to air some of these views, I agree with the group that the more public support and high-profile discussion we can get around the spec the better — it’ll eventually all filter down to the WHATWG mailing list anyway.

“We, the undersigned, wish to declare our support for the direction in which the HTML5 specification is heading. Its introduction of a limited set of additional semantic elements, its instructions on how to handle failure, and its integration of application development tools hold the promise of richer and more consistent user experiences, faster prototyping, and increased human and machine semantics.”

The HTML5 Super Friends have a list of technical hiccups and problems in the spec. Positively, they have also proposed solutions:
http://www.zeldman.com/superfriends/guide/

The Spec
Just the markup parts of the spec, omiting much of the browser implementation stuff
http://dev.w3.org/html5/markup/
and a one-page version
http://dev.w3.org/html5/markup/spec.html

Nicole Sullivan/Yahoo!
Nicole Sullivan of Yahoo!, and also a Super Friend, gives her thoughts on the HTML5 spec, with particular focus on bringing Standardistas and JavaScripters together

“It should be possible to do more with less javascript. I’d like to see browser support for common aspects of web pages as well as web applications. Practically every site in the known universe has toggle blocks, tabs, carousels, or accordion menus. I’d like to seen native browser support and CSS styling, so that these element incur no particular performance cost.”

http://www.stubbornella.org/content/2009/08/31/html5-who-is-bad-enough-to-take-on-canvas/

links for 2009-09-14

Monday, September 14th, 2009

links for 2009-09-09

Wednesday, September 9th, 2009

links for 2009-09-08

Tuesday, September 8th, 2009

links for 2009-09-07

Monday, September 7th, 2009