A couple of weeks ago I went to a workshop run by Philip Fierlinger of Xero fame, all about Flash prototyping. It was generally a good session, and although there wasn’t anything particularly new that I learnt about Flash - looking at Philip’s prototypes opened my mind to the possibilities of using it for a few upcoming projects at Chrome. Here’s a brief screenshot of the control buttons in Philip’s tutorial templates.

Phillip's Flash Controls

Phillip's Flash Controls

And here’s the simple prototype I made in the workshop - even though the workshop was focused to a Powerpoint “slide” style of building, I found it just as quick to build a “buttons” style prototype to give the user open access to the functionality.

Hit the pic to see the prototype in action.

Screenshot of Flash Prototype

Screenshot of Flash Prototype

So I’m almost finished my second prototype for a project, and today we presented to a client and I showed a Flash prototype instead of a boring old static set of wireframes. In a few words - it went extremely amazingly well. So well in fact, that because this is a new client we’re dealing with, I was half wondering whether it was just the client and not the process. But I must say - this is the first time I have ever presented and not really had even a single question at the end. After 20 minutes of showing them the prototype and talking about it they knew exactly what they were getting, so we ended up waiting for the designer to show up. Done and done.

I recently read an article about Flash prototyping on Boxes and Arrows and there was a lot of critiscism about length of time it takes to build, and ending up with something that can’t be used further down the track (as in the case of CSS/html). But the prototype I built took about the same time, if not a little less than a Visio diagram, and I didn’t have to answer any functionality questions which looks like it will save time in the long run. I even built my IA site map into a fancy little button in the top left hand corner of the prototype. Seems like it’s all win win to me.

There are many different tools for prototyping that an Information Architect can use to author sitemaps and wireframes. I’ve never personally found a tool that I’ve been 100% happy with. The most common prototyping tool would have to be Microsoft Visio (which is what I use mostly) which allows for extremely rapid prototyping with a moderate amount of customization for doing live user testing. There often seems to be tension between a full GUI (Graphical User Interface) and dynamic code producing tools for testing purposes. Some of the most well known tools among others are Axure, IRise, Omnigraffle, Flash, Photoshop, Fireworks, Illustrator, InDesign, Freehand, Powerpoint and even Ruby on Rails. Below are screen views of Visio, Axure and Omingraffle. For the most part Axure is the only product focused to application and site design. But it falls down in the limited number of template elements that it has, and the inability a user has to create their own template elements. The screenshot from Visio is from a contact form page that I recently authored as part of an Information Architecture.

Omnigraffle

Omnigraffle

Omnigraffle Interface

Visio

Visio

Visio Interface

Axure

Axure Interface

Axure Interface

I have once again (sadly) become a time poor person as I finish a paper at Victoria University. I have had a heap of ideas, and developments on the IA front, but haven’t had the capacity to muse about them, which makes for a much less creative me. The stack of snippets and segments I want to write about is slowly amassing in my briefcase folder, and who knows if they will still be as relevant in the seven or so weeks it will take for me to finish… But the good news is that the energy that otherwise would have been expended from musing, is currently being directed to this 4four12 project. And it’s coming along swimmingly.

Last.FM has just recently undergone a major site overhaul. I love de-constructing websites when they are re-built and trying to gauge the decisions behind why they might have done this or that. There are a lot of large sweeping changes in this re-design, and typically from experience with sites and users, I know that this has the potential to ruffle a lot of feathers with the loyal fans. But that is not so big a deal as long as the changes have been made with the right amount of user testing, based on what users want. After a small amount of time users wonder how they ever got by using the site without the new functionality. But is that the case with Last.FM, and are there other factors that might hamper the acceptance?

The Deconstruction

I’m mainly going to focus on the main navigation and core functionality for this.

First of all, let’s start with a brief (and by no means exhaustive) history of Last.FM.

Homepage

Circa 2005

Circa 2006

Circa 2007

Today

Dashboard

Circa 2006

last.FM dashboard screenshot 2006

Circa 2007

Today

last.FM dashboard screenshot 2008

New layout – The Good

From an Information Architecture point of view overall the layout is better.

They have obviously focused to the tools, and the ability to use last.FM as a tool to find-out more about music that might appeal to the user. This is apparent through the large amount of screen real-estate dedicated to “recommended content”.

The friends list functionality has been expanded, and there is now data available as to what track each of your friends has most recently listened to.

The search functionality is much better. Having the drop-down box that allows a user to search the specific areas of the site.

The top right dashboard drop-down is also quite good. But in my opinion it is too simplified, and not prominent enough. The Circa 2006 top-right dashboard area, from a layout perspective was much better.

The new media player seems much improved, although they probably could have just put the media in a persistent spot in all the pages, and saved a click through.

New layout – The Bad

There are a fair amount of decisions that in this IA’s opinion probably spent too long being discussed in internal focus groups, and have ended up worse off. Or potentially even worse were not discussed at all. Why you would want to know what you have just listened to under your profile is beyond me – surely your ears and brain could tell you the same information a lot faster.

The images of recently added content are very large. This looks OK when the design is viewed all at once in an “entire page format”. But when the browser fold is added they hog a lot of the screen real estate. I have dual 1680×1050 monitors, so it’s definitely not just my screen res.

New layout – The Ugly

I have a real problem with the design. I think that the IA has been executed in an average to satisfactory manner all things considered. But the design doesn’t do it any favors. The banner across the top looks like it was done by a fresh grad who just found the latest cool grunge photoshop brush set on deviantart.com. Where the previous site employed the use of gradients and contrast to “pop” sections of the design out, the new site is flat, and a lot of the content competes for the user’s attention.

Another design bug-bear is that where they previously had a unique and easily recognizable site that had strong brand presence and was very clear. Now they seem to have totally de-sanitised the site to the point where if you linked straight to Facebook (or a number of other minimal flat websites), a user might not realize that they had even changed sites. It has gone overly clean and in many of the wrong ways. The contrasting text colours don’t really complement each other, which would be fine if it was for the sake of contrast and information hierarchy, but they don’t seem to serve this purpose.

The left hand menu is an after-thought. It is small and insignificant and doesn’t seem to hold enough options. It is obviously the “user menu”, but why double up on the dashboard drop-down box and then only include half the items? It just seems clunky.

The summary

The motivation for many of the changes seems to have come from a direction of utilizing the site to create more revenue. Examples of this are as a tool for the music industry to gauge statistics, and sell information, and also the new advertising sections on the site which are much more prominent. I have no problem with sites wanting to make more money, but a lot of this seems to have been executed at the expense of the user and their profile. Surely if their commodity is data, then the idea is to encourage folksonomy, and user input. But they seem to be relying too heavily on the user-side software that simply logs data via itunes or wmp.

Anyway, I hope that things move in a more positive direction with the next re-vamp, as I love last.FM, and have come across quite a few artists whose CD’s I have bought because of them.

The webby awards site has a really nice flash interface for browsing the 12th annual webby awards nominees and winners. In short all the sites up for a silver spring are represented by a small icon about the size of a favicon. Then there are filters that can be applied located along the bottom of the interface to filter by winner type, media type, trends, and location. There’s been a couple of times where I’ve been browsing the categories to see what’s what, and been frustrated by the long extended pagination of the site. The flash previewer deals with browsing fantastically though.

« Previous PageNext Page »