I would say give programmers all the results of your work as they move into development. Don't make assumptions regarding what they will find useful or what they will understand. The best programmers "get it" and want all the info. The best thing you can do is bring programmers into the project early and work collaboratively in areas of overlap (like IA and wire framing).
If you give them a list of specs then all you'll get in return is a set of functionality. Share the process with them and the result will reflect their deeper understanding. Similarly, you may find that your work is better informed and fully leverages the technology if you maintain a dialog with programmers through out the process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=28356 ________________________________________________________________ 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
