Hrm, opposite for me: http://www.jessewarden.com/archives/2006/02/prototype_solut.html
In fact, most turn into projects if you aren't careful. I've found, if you have a talented designer, you're best bet is to get them to create mock prototypes to get in front of users quickly before the actual developers imlement the interface. Change control is challenging in that the designer is responsible for not only keeping track of what changed, but informing her manager who in turn informs the developers. Prioritizing those changes is also challenging because developers obviously think functionality is more important, but it's not their call really. ----- Original Message ----- From: "Dwayne Neckles" <[EMAIL PROTECTED]> To: <flashcoders@chattyfig.figleaf.com> Sent: Wednesday, March 01, 2006 1:46 PM Subject: [Flashcoders] {Business/Workflow} The use of mock prototypes Hello folks, Just wondering when you are developing flash site how many folks actually develop flash prototypes or fake quick mock up of how the site functional will feel...it seems like a waste of time to me especially with larger projects... but if someone didnt mind sharing their experiences on whether one should I'd appreciate it. Thanks, Dwayne dnecklesportfolio.com _______________________________________________ Flashcoders@chattyfig.figleaf.com To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com _______________________________________________ Flashcoders@chattyfig.figleaf.com To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com