Hmm... okay, I think I'm getting it. When I was at AOL, for usability testing, we'd create a Flash version and test users on it. It wasn't the application at all, really -- just something that looked and behaved like what we wanted to develop. That Flash version, if I'm understanding the input here, is really a prototype... right?
On Mon, 17 Mar 2008 03:51:46, John Wood <[EMAIL PROTECTED]> wrote: > I don't think of prototypes in trms o the fidelity of representation, > but rather in terms of functionality. Any flat, drawn representation > is a wireframe, whether turned out as a series of grey boxes or as a > luscious photoshopped mock-up. Add behaviour at any stage, even > something as simple as links in Visio or Omnigraffle, and you have a > prototype. > > I think this is the key to he difference in the minds of software > engineers. To them, a prototype is created in code and therefore has > moving parts (even if they lack full functionality). To them, a > drawing is a drawing, a prototype is something you can play with. > > > . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . > Posted from the new ixda.org > http://www.ixda.org/discuss?post=27157 > > > ________________________________________________________________ > 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
