Seriously Cool Headphone Packaging

This concept design for Panasonic's 'Note' headphones, whilst strangely reminiscent of Apple's recent packaging, goes one better by using the headphones themselves to make the shape of a pair of quavers. How cool is that? Clever and simple. I like.

Tagged Design Link

Font Wars

LOVE IT!

Tagged Design Link

The Apple Tablet User Interface

A very interesting Gizmodo post about the user interface for the mythical Apple tablet.

Profile of Jonny Ive

I love this clip - it's pretty much an Apple advert even though it isn't but I do think Jonathan Ive is a man to be admired.

Tagged Apple Design Video

When should you use Comic Sans? [diagram]

 

Tagged Design Link

Popular Logos with Hidden Symbolisms

see them all at: sixrevisions.com

Great stuff - I've always liked the FedEx one, but there's a few here I hadn't spotted.

Tagged Design Link

The forgotten cost of features

A perfectly blank sheet of white paper is a tool of infinite possibility. For input you could use a pencil, a pen, a crayon, a marker, a stamp, a brush or more. You could use all of those at once. You can write or draw or paint in any direction. Even multiple directions on the same sheet. You can use any color you want. How you enter data onto it and how that information is structured seems almost limitless. That flexibility and power is available to you because of it’s lack of features. In fact, it is featureless - devoid of them.

Let’s add a feature. Let’s put some ruled lines on the paper. Make no mistake, this feature adds value. It allows me to be able to write neatly by using the lines as a guide. This makes the data more legible by providing a structure for me to follow. It also has a cost. It takes away some of the flexibility. Could I still write sideways in opposite direction of the lines? Sure. Am I likely to? No. Why? Well, it would go against the provided structure and thus make the data less legible. Ruled lines would intersect and, to a small extent, obscure my words and drawings.

OK, next feature - A box at the top left corner of the short end of the page. Perfect. That empty box has some value. Perhaps I could write a date in there. Perhaps I could use a colored marker to fill it in - color code the page. Perhaps I could put the name of the project that this piece of paper belongs to. Does the box take away from the available free space on the page? Sure it does. It is a trade off though. What I give up in space I gain in value right? Well, that depends on the perspective of the individual, but I think I like it.

Enough on that. Let’s add a feature to that box we added. Lets pre-print what we think people should use that box for. You know, to make it clearer for the end user. Let’s print a label in that box called “Title”. Perfect. Now I have added value by reducing the amount of thought a user of this paper has to put into figuring out why that box is there, right? I think you can now see where I am going with this…

I think it is far too easy to look at the addition of features to anything - hardware, software, analog, digital, even a simple piece of blank paper - as a benefit without also recognizing the associated and often forgotten cost.

In the world of hardware and software, the companies, developers, and tools that get it right weigh the cost of adding features heavily and take every feature addition under great consideration. In fact, they reject most feature requests right out of the starting gate. They appreciate feature requests but more often than not read them and ignore them. They simply let the signal rise above the noise to determine what features to add. When they do add a feature, they do it in the most unobtrusive and seamless way possible. They are careful to make sure the value far outweighs the cost.

The costs do not stop there. In fact, if you add a feature you now have to support that feature if it breaks or does not work as the user expects it to. Also, adding a feature could actually lose you a sale. Those of us (I am not alone) who are feature wary may opt for something else just for the simplicity.

This does not mean that you cannot have a ton of features yet still maintain flexibility. One example is TextMate. TextMate is a very powerful text editing program for the Mac. It is chock full of features and has a robust plug in architecture that allows you to add even more. Yet all that power is hidden in the UI. When you launch TextMate all you see is a blank white page ready for input. The features are not in your way. If you just want to get some writing done in plain text you have the only feature you need right there. The power is not there unless you need it and then mostly as a menu item optionally accessible via a keyboard shortcut.

On the other hand, Notes.app on the iPhone is very basic in features. You can take notes, you can email a note, and that is about it. But that is what makes it great. You can use Notes.app any way you want. Type up a blog post draft. Enter in a book recommendation. Make a shopping list. Note the dimensions of that room you need to buy furniture for. In fact, it’s lack of features and structure are what provide it’s true power.

As you can see from these two disparate examples, It is not about not adding features. Features in and of themselves are not a problem. It is about adding the right features and only the right ones. I like ruled paper with a predefined area for a title and date just like the next guy. It is about understanding that for every added feature there is a cost and not forgetting to consider that.

This is a great little article. It's on a theme I've been planning to contemplate in a blog post of my own - simplicity. It's what makes Twitter great and what often - though not always - pushes Apple ahead of its rivals. Interesting stuff...

Tagged Design Link

R&D Workspaces: Some Quotes

One of the challenges I work on in developing BBC R&D North's new premesis (both the interim solution and our long term base at MediaCity:UK) is figuring out just what we as a department need to do our work. I've talked a little about the technology, but the physical environment is important too. Just what makes a space that engineers can work effectively in? I'd love to hear any suggestions you may have (use the comments), but I also thought I'd share some quotes I found when trying to quantify and communicate the environment we're trying to create.

Read the rest of this post »

Death By Powerpoint

I've just spent the day at Futuresonic, the Urban Festival of Art, Music & Ideas in Manchester. The talks I saw ranged from the unintelligible to the inspiring, but on the whole it was an enjoyable day. I was particularly impressed by Aaron Koblain's talk on data visualisation. I shan't relay what he said, but instead will simply suggest you check out some of his amazing work at his website.

What the day also got me thinking about however was the quality of presentations. Every presenter I saw today used some sort of computer presentation, all run on the venue's Macs running Apple's Keynote software. However it was clear to see which presenters had written their presentations in Keynote and which had put them together using Microsoft Powerpoint. Reason 1 was that Keynote's ability to import Powerpoint files isn't quite perfect, making for some slightly oddly aligned fonts. Reason 2 was that I recognise some of the templates provided by both pieces of software. But reason 3 was that the presentations run on Keynote were - without exception - quite simply better than the Powerpoint ones. I couldn't help but wonder why - both pieces of software offer similar functionality, so why would users of one program produce better presentations than users of the other?

Read the rest of this post »

Pres and Cons

I'm starting this post with about 5 ideas in my head of what I want to talk about, and they're only loosely connected. This is probably not a good way to write an engaging and well structured post, so I apologise now if it's a bit rambling and rubbish. But bear with me; hopefully I have some interesting things to say, and I definately have some interesting links to share.

This week at CES, Palm announced the Pre and webOS, a new touch-screen smart phone and its associated operating system. Cue much media hype, cries of "iPhone Killer" etc etc. I got dragged in to the story a bit and my initial impressions were very favourable, however after a bit of reflection the story is a lot more complex than it looks, and interesting not just because of the Pre itself, but what it tells us about the iPhone, Blackberry and even media coverage of technology.

Read the rest of this post »