Helen,
Most importantly, Axure does not produce production HTML code (you
can't even use parts of it), it's only meant to be seen on a browser.
Although it has a clunky UI, the learning curve is very fast. The
documentation wasn't very useful for me, so you should explore that
further. Search for Axure in the archives- there have been more than a
few discussions on this topic.
Vishal
Sent from my iPhone
On 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
________________________________________________________________
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
