Archive for: September 2009

iphone web app updated

September 28th, 2009

After the initial buzz of getting this website onto the iPhone, I decided to have a closer look at the code that Dashcode had churned out. I came to the conclusion that it was pretty crap, so started looking around for alternatives and stumbled across IUI, a JavaScript library that restyles your semantic XHTML into iPhone-styled screens.

The result is this, a semantically written set of XHTML templates which work across all graphical browsers and a iPhone-specific look and feel for (yes you guessed it) the iPhone.

Now I can relax and get to work on learning how to write my first iPhone App!

Information Architecture: size matters

September 25th, 2009

For the past few days I’ve been working from home and decided to take advantage of our new flat screen TV (as you can see below).

The resolution isn’t as high as a Mac flat screen, but at 32 inches the wireframes are almost popping out of my screen.

Sometimes you just have to go BIG!

The ultimate mac set-up?

Graphic Designer vs Client

September 25th, 2009

My friend Beej sent me a link to this video today Graphic Designer vs Client. Its a short, tongue-in-cheek clip about the trials and tribulations of working in the industry we work in (Digital) and it made me crack up (more so because some clients are actually like this – or worse).

Hungry Browser OS X Widget

September 15th, 2009

Following on from my tinkering with Dashcode at the weekend I thought I would try my hand at developing a simple widget for OS X dashboard. The widget simply takes the most recent posts from my website and feeds an excerpt in via RSS. Users can adjust the length of each article. Clicking on a headline takes the user to the respective article on my website.

Download the widget (you will need to be running a Mac with OS X 10.4.3 or higher).

Front view of widget Back view of widget

A little bit of home grown and a spot of picking

September 13th, 2009

This year was my first year trying out the art of home grown vegetables. I always thought this was reserved for old people and/or folk you see on TV, but I was inspired this year to try my hand at it.

Well what can I say, it’s on the whole been a big success. I’ve had rocket, lettuce, tomatoes, courgettes, herbs, carrots, chilies, sweet peppers and runner beans. The only thing that got munched (not by myself) by insects was my second installment of rocket. Apart from that it has been a summer of garden goodness.

Also to note is that we have a load of woodland and hedgerows in this neck of Essex, and so I have managed to pick about 3kg or so of Blackberries this summer. The last of which I picked today along with some apples which will probably be going into a crumble and some smoothies this week!

herbs

lettuce

sweet peppers

tomatoes in bowl

apples and blackberries

tomatoes on plant

chili on plant

Sony Ericsson website information architecture

September 13th, 2009

Whilst working at Dare Digital this summer I was involved with the redevelopment of the user experience for the forthcoming global website relaunch. I worked alongside the in-house IA, design and account teams to develop the documentation for the site (Wireframes, Sitemaps etc.). I also attended internal and external meetings and conference calls with the client.

Sony Ericsson

Deliverables

  • Sitemap
  • Wireframes

Client goals

To redevelop the entire Sony Ericsson website user experience and position Sony Ericsson products at the centre of this experience.

Challenges overcome

As I joined the project three months after the launch date there was a lot of catching up to do. This took time and effort, but eventually I was comfortable leading internal meetings and making decisions that effected the direction of the IA and design.

On a slightly less serious point, the entire project documentation was produced using Visio. This was a real pain in the a**e as I am a Mac person and have a strong belief in making anything look as good as possible. This simply can’t be done efficiently and without a lot of headaches in Visio. Needless to say I wasn’t a happy bunny for the 4 or 5 weeks that I was involved with this project, but sometimes you have to bite your tongue and get on with it.

The new website is due to go live some time later on this year.

Hungry Browser iPhone Web App

September 12th, 2009

I was tinkering around with the Apple iPhone SDK this morning and after a few hours of fiddling I decided to use Dashcode to create a little iPhone Web App. The app simply delivers the most recent 10 posts from this website and formats them into a list. Clicking on an item previews the post. Subsequently clicking on the “read more” button sends the user to the respective post (in full) on www.hungrybrowser.co.uk.

It isn’t going to set the world alight, but it is a start. If you have an iphone and want to follow the content on this site (and don’t want to keep on loading the full site), then simply click on the icon below to go to the iphone Web App version at: www.hungrybrowser.co.uk/benellis/iphone/

Enjoy!

iphone screen

Hungry Browser iPhone Web App

Vodafone Nightwatchman information architecture

September 11th, 2009

Overview

The Vodafone Nightwatchman website was developed as a counterpart to the Street Sixes website (a series of street cricket competitions that took place in the run up to each Test Match during the summer of 2009).

The objective of the Nightwatchman website was to raise awareness and open up cricket to a new audience. This was achieved through a series of tongue-in-cheek film clips reporting on the action and breaking the moves and jargon associated with cricket.

Vodafone Nightwatchman

Deliverables

  • Sitemap
  • Wireframes

Client goals

To raise awareness of the Street Sixes competitions and to open up cricket in a tongue-in-cheek way to a new audience.

Challenges overcome

Due to the phased nature of the the events, the site’s content would evolve over time in both the depth and breadth. It was a particular challenge to devise a way to represent future content without showing the site as having gaps where future content would eventually sit. The second major challenge was deciding on the degree of interaction the site should offer and create appropriate functionality to serve user needs without over-engineering the site.