Need to build a prototype, but don't know what to use? There are many factors that will likely seem to influence that decision, but there is only ONE that matters:
What is the prototype going to be used for?
Some types of prototypes:
- Prototype as documentation
- Prototype as pitch
- Usability prototype
- Experimenting through prototyping
Each of these has its own set of high-level goals, and picking the right prototyping tool will help you achieve them. First, here's my cut of the top (and interesting new) prototyping tools. There are many more of course, some I ignored on purpose, some I totally overlooked. Fill me in, please.
The usual suspects
iRise
Very popular in large enterprises, often argued as a means for business analysts to concept solutions.
Allows you to have data driven prototypes which can be very high or very low fidelity.
$$$$$ ($6,995)
Axure
Similar in many respects to iRise, Axure seems to be more oriented for designers. Visio-like interface with common libraries.
$$$ ($589)
Balsamiq Studio
Very compelling interactive wireframing tool. Less specification-oriented, very much a graphical UI designer.
$ ($79)
Fireworks CS4
The old is new again. Back in 1999, I used Macromedia Fireworks all the team to comp out new designs and make them interactive. It's now built into CS4 and goes as far as letting you build AIR apps.
$$ ($299)
Expression Blend 2
Build interactive UI prototypes much like you would build a Flash app. UI can be exported to let the developers get a jump on UI coding.
$$$ ($499)
ProtoShare
A new one to me (thanks @virgosun!) Lets you build clickable wireframes in a collaborative tool.
$+ ($29 - $199)
Paper
Drawing on paper and paper prototyping are by far the cheapest and best means to get your concept out. Also included in "paper" should be any UI editor you currently use: Visio, Omnigraffle, Illustrator, etc.
FREE
So which to choose when?
Deciding which on to choose is not always easy, especially when you have enterprise consistency to be concerned with. Instead of being prescriptive, here's what I think is most important for each of types of prototype above.
Prototype as documentation
Developers & business partners need to understand you (but they don't usually speak the same language). This argues for fairly high-fidelity documentation. A semi-functional prototype with integrated documentation would be best.
Winner: Axure
Runner-up: Protoshare
Prototype as pitch
This needs to be high-fidelity, flawless in execution and interactive. Stakeholders need to be able to glean the sexiness of your execution and the vision of the direction.
Winner: Fireworks
Runner-up: Expressions
Usability prototype
Needs to be fast and representative of core interactions. The ability to create derivative prototypes for new studies is important.
Winner: Paper
Runner-up: Fireworks
Experimenting through prototyping
You need to be able to try new things without being fussy. Sketches are good for getting a general idea, but at times you have to go deep in order to understand if critical usage scenarios will hold up.
Winner: Balsamiq
Runner-up: Paper
