Due to a few key typos, I'm not entirely sure what you're asking, but I'll give it a shot ...
> Do make a distinction between iterative > designing, and deliverables? I do protocasts iteratively, just like wireframes and prototypes. I just use these "protocasts" to further illustrate how something is meant to work. I don't create prototypes for entire apps all that often - usually, I just protoype individual interactions and send that along with the protocast. I would describe your Protocast as a > Mockup. Um ... ok. I don't understand your point. My thinking is that its important to understand the audience > for anything I'm working on. Be that an audience of myself as I'm > sketching on paper, or a larger group. I'm not sure what this has to do with the subject at hand. Robert, is your output all 'prototype' or do you switch over from > throw-away designs to deliverable work at some point? Not really sure what you're after here, but I'll attempt to answer. I use wireframes and storyboards extremely often, prototypes less often, and protocasts on occasion. Depending on the project, either the work ends here, or we stick around and do usability reviews and such as a site is developed by a client's in-house team, or we build it out to completion and deliver the final site to the client. I don't consider wireframes to be "throw-away designs". I archive these and continue using them with every new project/iteration for the same app/site. -r- ________________________________________________________________ *Come to IxDA Interaction08 | Savannah* February 8-10, 2008 in Savannah, GA, USA Register today: http://interaction08.ixda.org/ ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://gamma.ixda.org/unsubscribe List Guidelines ............ http://gamma.ixda.org/guidelines List Help .................. http://gamma.ixda.org/help
