I really appreciated the fantastic responses to this list (and off list) with regards to using Axure for prototyping and the learning curves, ability to import Visio, and whether it produces production ready (and WCAG compliant) code.
Based on everyone's feedback, I have recommended using this tool for a massive project that has aggressive timelines. I've been working with Axure in the evening hours and I'm impressed with its potential. My new question: Has anyone experienced the situation where professionals (not trained in the field of interaction design and User Experience) have taken this same tool to heart and have created prototypes that truly violate principles of design, but they see how quickly they can produce a prototype? How you do you handle it? Thanks in advance! Helen On Thu, Jan 29, 2009 at 7:44 PM, Helen Killingbeck <[email protected]>wrote: > Thinking about using Axure for prototyping as there are many great benefits > from a documentation point of view. > However I am wondering about the learning curve and the ability to import > previously documented high level page structures (Visio) > > > Questions > 1. What would be your estimate regarding the learning curve (timewise) to > becoming productive with Axure without feeling like you are blowing the > project timelines for deliverables? > > 2. Can you import Visio drawings into Axure? > > 3. My understanding is that Axure produces html code. So how compliant is > the code when trying to ensure WCAG 2 compliant code? > > 4. What are the downfalls of using Axure? > > Thanks in advance. > > Helen > > > ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [email protected] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
