Re: [IxDA Discuss] Question about streamlining Axure prototypes, Feb 3
If you remove all of the unused pages or layers from your prototype, then save it with a different name in a different folder, it will save only the files that are in the current prototype. If you need to revert to the original name, you can delete the old prototype, then rename the new one with the original name. Hope this helps. - Original Message From: Gloria Petron gpet...@gmail.com To: IXDA list disc...@ixda.org Sent: Wednesday, February 4, 2009 12:13:12 PM Subject: [IxDA Discuss] Question about streamlining Axure prototypes, Feb 3 Hello, I'm generating an Axure prototype that's morphed quite a bit over time. How can I clean up the prototype folder to get rid of unused files and folders? I don't see a Clean up/remove unused files feature on Axure. Does one do this manually? Thanks! Gloria Welcome to the Interaction Design Association (IxDA)! To post to this list ... disc...@ixda.org 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 ... disc...@ixda.org Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Axure - Questions...and more questions
I agree with pretty much everything Becky said about Axure, though I would add that while it's easy to pick up the basics of Axure, it does take a little more time to figure out how to put together the interactions. Part of this is because there are lots of things the software won't let you do easily, but if you know the software well enough, you can find ways to fake it. In some cases, I spent lots of time putting together a prototype thinking I could get something to work one way, then I'd have to go back 'cludge' something together to make it work the way I wanted it to. This is yet another reason never to expect Axure prototypes to be development ready code. Another thing to consider is the presentation quality and visual fidelity of Axure. As Becky pointed out, there isn't very many options on how you can make text appear, and Axure prototypes are generally very low fidelity and aren't very pretty. If you're using them just to work with developers and 'concept' or explore different interactions and navigation structures, Axure is great, but I'm not sure I would ever use Axure wireframes as client deliverables (depending on the client, of course). Also, printing is iffy. You have to structure the layers on the page so they don't appear when you print pages, which may be contrary to the way you want the prototype to work. I definitely used it in conjunction with Visio, but I would create jpgs of Visio wireframes (that I had done for other parts of the site, or that had more graphical and page elements on them - headers, footers etc.) and then I would add layers or other elements to show interactions. As far as I know, there isn't a way to 'import' Visio work you've already done and move forward from there. Kim Welcome to the Interaction Design Association (IxDA)! To post to this list ... disc...@ixda.org Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Agile UXD
My experience is that you as a UX person need to be involved in the product definition or 'backlog' throughout the entire development process and not just the beginning definition phase. Sometimes you will need to be more of a product manager than a UX person, and be willing to limit or streamline the amount of documentation you end up doing (not necessarily a bad thing). Just In Time Design is an Agile mantra Be flexible and work directly with developers as a team, not just delivering specs and wireframes then moving on. It is important, however, to have a good strategic vision to build from, which can often be the most challenging part to fit into an agile process. There is the concept of sprint 0 - that this is the intial sprint where you work out all of the high-level strategy and IA structure then create your backlog from there. I personally like to have specific UX deliverables or demos in each sprint so that UX and possibly design stay 1 sprint ahead of the development team. The demo for the UX team is wireframes or a clickable prototype that is presented to the group. Jeff Patton has some interesting ideas and tips about UX and agile http://agileproductdesign.com/blog/ Hope this is helpful. Kim - Original Message From: Jessica Petersen [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, November 3, 2008 4:50:45 PM Subject: [IxDA Discuss] Agile UXD What are your experiences in an agile environment? What has worked for you and what hasn't? My organization is considering employing agile, and I tend to be of the opinion that UXD needs to be at the forefront of the process thinking about things holistically - then breaking the project into chunks that will eventually result in a complete user experience. However, I have received quite a bit of push back in this regard and have found it difficult to find other experiences which support my thoughts. Thanks, Jessica Petersen Senior UX Designer [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] 801.722.7000 x 1483 tel 801.722.7001 fax 550 East Timpanogos Circle Orem, UT 84097 www.omniture.com http://www.omniture.com 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
