what's the obessions with Visio?/Prototyping tools
6 Apr 2006 - 1:53pm
8 years ago
In my experience it seems the more a group has the resources/headcount, the
higher the fidelity of a prototype is possible. If it's a small company, or
more developer/non-designer oriented, prototyping tools seem to fall along
the lines of Visio, PowerPoint, MS Paint, and paper napkin ;) Visio is a bit
of a standard as it has a large install base, people are comfortable with
Office products, and no coding required.
In usability testing I have seen valuable data coming from both highly
interactive applications as well as paper prototyping. What tool to use
obviously depends on your overall goal, but higher realism requires
expertise and time.
Personally, I use Director for rich "click-thru" type demos and prototypes
(a linear series of events that will be presented to an audience or tasks
for usability). Flash for non-linear simulated application prototyping.
..but sounds like the product has not been killed. I was very interested in
this App as it promised true devloper&designer integration (XAML). In my
limited use with the app and public forums this came across as more of a
developer tool than Flash (but new apps require new thinking!).
[Please voluntarily trim replies to include only relevant quoted material.]
How about Sparkle? Did anyone already try to use it for Prototyping?
On 4/5/06, Pashmina <pashmina at gmail.com> wrote:
> [Please voluntarily trim replies to include only relevant quoted material.]
> > I'm quite curious about everyone's general feelings about Visio. I see so > many job descriptions where Visio is a required software skill for IA or > IxD's and I just don't get it! What is the obsession with Microsoft > Visio?Who set > that as a standard? When did it become a standard? > > Personally, I can't stand Visio, and I won't to use it to mock up wireframes
> or process flows. I find that powerpoint can be very useful because you can
> send those to anyone. And I particularly like using Flash to make mocks, > because both the designer and coders are happy with Flash too. Designers > can add a layer to my frames and start putting in graphics and interface > elements. The coders can use the pixel guides to break it down into CSS. > > Visio in the hands of a somewhat decent IA, but with really horrible > awareness for interaction design, can just become a nightmare. > > Anyway, I don't understand how a field so new, could have job req that limit
> the types of tools we use in our practice. > > pashmina > ________________________________________________________________ > Welcome to the Interaction Design Association (IxDA)! > To post to this list ....... discuss at ixda.org > List Guidelines ............ http://listguide.ixda.org/ > List Help .................. http://listhelp.ixda.org/ > (Un)Subscription Options ... http://subscription-options.ixda.org/ > Announcements List ......... http://subscribe-announce.ixda.org/ > Questions .................. lists at ixda.org > Home ....................... http://ixda.org/ > Resource Library ........... http://resources.ixda.org >