Perhaps I am in the minority here but I think it is really important to have models to show people. Architects have done this for years, showing building concepts as foamcore models so people who are not adept at reading blueprints can see the concept clearly from many angles.
To say that a prototype=code and is the domain of the developer, to me, is to construct a rather narrow definition of the term. If the result of that narrowness is for interaction designers to say that they only deliver on paper, I think our ability to communicate will be reduced. And perhaps, so will the quality of our thinking, since sketches are often less detailed than models. I have always found it useful to show people models of my designs. And if I can get the models to show state, all the better. Perhaps we should not call these models prototypes but neither, in my opinion, should we ignore them Charlie . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=25888 ________________________________________________________________ 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
