A common point of confusion when I've partnered with other
IAs/Interaction Designers/UX Designers, yadda yadda yadda is what a
wireframe is vs. what a prototype is. Everyone seems to have a slightly
different take on them. Here's how I differentiate:
Wireframes - standalone "illustrations" of screens void of graphic
treatment, with indications of functionality and screen flow.
Prototypes - interactive versions of screens with varying levels of
Title: Lead Interaction Designer
Location: San Francisco
Salary: 90's + bonus + stock options + outstanding vacation and benefits
An innovative, global financial institution is seeking a Lead
Interaction Designer with experience in Web applications, interaction
design, product development and usability. This is a unique opportunity
to join a small creative group with enormous influence in shaping one of
the most commonly used financial sites globally.
All drawing and diagramming tools that we use to create wireframes are based
on shapes or widgets. You drag a widget from a palette and drop it onto the
page, then set its position and size with mouse. The operation is easier if
the editor supports snapping to the grid and guides.
I wonder however if this is the optimal way of drawing wireframes, because
it doesn't account for their peculiarities, namely:
* Content rectangles never overlap each other but cover the entire page
* Content rectangles are mostly aligned in columns and rows, i.e.
My team is evaluating wireframing tools, and I would love to get some
feedback from this list. Things tend to be leaning towards Visio at the
moment. Being a designer, I'm not too thrilled at the idea of using