Home >
Any quality development team will put an application prototype before their clients before every starting on production code. There are many many software packages to help make this a quick and easy process. We would like to know which in the list provided is the one that you use most often. Please click here to take part in this week's poll.
I am sure that there are some titles that I left off the list, please let me know within the comments of this post and we will try to get them added as choices.




Facebook Application Development
Hi Rich,
we at FullSix Portugal use Microsoft SketchFlow.
Cheers from Portugal
We use Creately (http://creately.com). Flexible and collaborative.
I use mostly Adobe Fireworks; and when not using Fireworks, then sketches on paper ;-)
Really nice sketches on paper, then Flash (since I use the drawing tools so much and will develop in it anyway)
Hi Rich, my favorite prototyping tool is ForeUI, but you misspelt it to "ForceUI" ;)
I selected Balsamiq because it was the one on the list that I use... but I tend to do actual prototypes in Flash directly, since I typically use the prototype as a starting point for development. Balsamiq helps to work out a general idea of the layout.
I use Illustrator almost exclusively. With the ability to create reusable symbols for prototyping and then exporting as Flex assets, it is the smoothest workflow for me.
Balsamiq mockups, it's the only type of prototype I can look at without physically vomiting all over the page.... Who wants to see screenshots of web software, cut up and thrown together again using Microsoft Powerpoint?.. anyone?!
Hands down - Adobe Fireworks. Anything I'm doing for the screen either starts or ends up in this application.
As Ross, I prefer to use Flash IDE.
No doubt, Fireworks.
Occasionally I use stickies and/or a white board for initial flow ideas, other than that it is mainly Fireworks. I use it for iteration mockups, for demoing flow, for doing the digital equivalent of paper prototyping where you ask users to figure out the flow, rather than placing cutouts on paper I introduce next steps in hidden layers or move the user to the next page.
Some of my interaction controls are done in Flex using view states (and a little bit with catalyst), but over all 95% of my time is spent in Fireworks.
I also like Fireworks ability to export- To pdf, to Flash slide show, to html, or keeping the document as a png. This flexibility is important.
Adobe FlexBuilder's design view is pretty nice for drag-and-drop building a quick prototype that runs on the desktop as an AIR application. When you're done prototyping, you can build it out to a full application.
I mostly use Illustrator.
You didn't add Justinmind Prototyper. Can you add it on your list?
thanks
flair builder, pencil html and photoshop.
ForeUI, I love its skinnable feature.
Other: Adobe FlexBuilder's design view works great for this. You have the flexibility to make it appear as functionally "complete" as you want (even up to faking server calls and such if you want), AND you can turn the prototype into the actual thing once it's finalized. Gets you a big head start.
I notice that a lot of people use fireworks for their prototypes. I love FW but don't find myself using it in a prototyping workflow that often. Questions for the people who use FW:
1) Does the bugginess and slow UI cause you problems?
2) How easy do you find it to move beyond simple click-through functionality in your FW prototypes to more complex behaviours?