Prototyping Tools of Choice
Prototypes come in all different shapes and sizes and have a variety of purposes. And there are a number of tools flashing their prototyping capabilties like iRise, Axure, Fireworks, and even Flex.
I've often been asked what's my tool of choice for prototyping and my answer is always the same - it depends. It depends on what I'm trying to do, what the business is trying to accomplish, and what we need to test or show. The goals of the prototype drive what tool I'll choose or recommend.
If all we need to do is test a few scenarios with little functionality, then a basic Flash prototype or series of images stitched together with HTML and some image maps will do the trick just fine. If we're testing high-level concepts and have an existing set of wireframes, then I might recommend doing paper - if I'm confident we can simulate any interactivity that is critical to the goals.
Right now, my tools of choice are paper (with my little toolkit of UI widgets), HTML/CSS, and Flash. However, I'm really excited about trying out Fireworks to see how it does. In fact, I've got a prototype project coming up next week that I might try using Fireworks for.
What about you? What are your tools of choice and why?
Comments
I've just played with Axure over the past day or so and I have to say I love it. I just read a review somewhere else about the wonderfulness of Fireworks (with the major drawback of not having functioning links). I'm going to give it a go as well, though. What I really like about Axure is that it's so intuitive. I was able to create a prototype in no time and the prototype and spec generators are so cool. After a few minutes of looking into Fireworks, it definitely would be uncomfortable for an Adobe novice (UI reminds me of Photoshop, but it's probably similar to flash too, which I stopped doing 6 years ago) so I'd think that's a drawback. But if it's as powerful, it's probably worth giving it more of a try since its price tag is definitely friendlier.
Posted by: Rachel | July 5, 2007 05:16 PM
I've started using plain XHTML/CSS/JS. Mostly because I already had the knowledge to do so, and it's just as quick as any other tool for me. I also like that it's not a throw away. It easily forms the basis for the final product when your working in a highly iterative and close-knit environment between yourself, other designers, and engineers. It's great to send to others too via email or throw on the web.
Posted by: Ryan Nichols | July 19, 2007 03:32 PM