I'd like to add that you don't need a highly experienced, high priced CF developer to create your HTML prototype. What works better is to have a graphic designer or pure HTML guy handle this and have an architect just looking over their shoulder.
The idea being that often pure HTML guys are considerably cheaper than CF developers. So if the front end of the application can be passed onto someone cheaper, then your company is much more likely to be profitable. Along with the fact that pure HTML guys tend to focus on how it looks and interacts with the user, which is a good thing. Steve hal helms wrote: > I highly recommend that the entire front end of an application be > created as part of the prototype process. I have seen many, many > failures occur when prototyping is either skipped entirely or (more > commonly) not treated seriously enough. > > -----Original Message----- > From: John Jonathan Kopanas [mailto:[EMAIL PROTECTED]] > Sent: Friday, June 07, 2002 11:27 PM > To: Fusebox List > Subject: FLiP and Prototyping > > In FLiP when you refer to prototyping do you prototype the whole site > i.e. do html pages for practically the whole site or just 2 to 3 > templates? > > Is there any tools other then devnotes used for prototyping in this > community? > > Thanks. > > John Jonathan Kopanas > [EMAIL PROTECTED] > ==^================================================================ This email was sent to: [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^================================================================
