I get kind of annoyed with these smug, pseudo-contrarian articles about, what boils down to personal preference. The right answer is: Use the right tool for th

I get kind of annoyed with these smug, pseudo-contrarian articles about, what boils down to personal preference. The right answer is: Use the right tool for the right job. * If it's a simple brochureware template, you might be able to knock it out in HTML from the start. * If it's graphically complicated, with a lot of rich visuals, starting in Photoshop or Fireworks may be your best bet. * If it is an application with numerous cases and a potentially complicated interface, starting with a clickable modeling tool, like Axure, might be the wisest approach. * Roll your own approach for a particular interface problem. Axure sucks for modeling mobile application interfaces, but hey, some dude figured out how to make a usable wireframing model with Keynote. I've used all three methods, and each has their advantages and tradeoffs. Personal preference often dictates how we work, but the project requirements may force us to re-evaluate these preferences in favor of a more efficient means of completing the project.