Wann nehme ich welches Werkzeug?

Diese Frage versucht Daniel Ritzenthaler in seinem Artikel zu beantworten. Er beschreibt, wann und wofür sich Skizzen, Wireframes, Mock-ups und HTML Prototypen eignen.

One designer will claim that you shouldn’t do anything without sketching it out while another claims that doing anything less than full-on HTML prototypes is a waste of time. All of these tools have a special purpose so there’s no point in discussing which one is better. That would be a lot like an electrician saying his wire-cutters are better than the plumber’s pipe-cutters. Within the context of cutting wires it makes sense, but everywhere else it’s just silly.[...]

This piece is about bringing clarity to this discussion. It will help you decide which tool to use without worrying what other designers are arguing about.

→ 52 Weeks of UX: Match the tool to the problem

Hirngespinster, ein Motion Book

Asking myself how to get into someones head visually, without loosing the connection to the real life, I finally came up with an interactive concept which transfers the real event into a book, and let the fantasy grow out of it animated.

→ Hirngespinster von Tristan Hohne

Prototyping im Detail

…erklärt uns Odette Colyer in ihrem Artikel Create the Perfect Prototype.

It’s much cheaper to change a website early on in the development process than it is to make changes later on. Building prototypes – draft versions of your website – is a good way of nipping problems in the bud and getting things right first time around. [...]

Your end prototype should be a fairly refined and testable representation of the product. There are several techniques you can use to reach this point, which again will be project-dependent.

Der Artikel lohnt sich, auch wenn die Gute hauptsächlich über Webseiten spricht.

→ Odette Coyler – Create the Perfect Prototype