I've run into some cases where the client didn't want the home page to become a PHP or ASP page by virtue of having the login or other forms on it. Whether this is a valid concern or not, I don't know.
Another possibility is that the login was added after the site went up and there was no room for it on the home page. Or the login has more than one or two simple fields. Or the designer didn't like having to accommodate login on every page and so stuck it on a separate page because that seemed tidier. My feeling is that, for a membership-based application, login should be available on every page of the external site in a consistent but out-of-the-way location. On Mar 12, 2008, at 2:15 AM, Howie C. wrote: > Hi, > > Anyone have any clue on the notion of why some websites have their > log in > fields presented upfront while some, prefer to just provide a link > to a > separate log in page? > What considerations should one take note of in order to make a better > decision? > > I know for sure that by presenting the log in fields upfront makes > it easy > for user to log in, especially so for social websites. But that > might not be > the main reason for doing so... > > Cheers, > Howie > http://user-experience.vox.com > ________________________________________________________________ > 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 -- Kim + + + + + + + + + + + + + + + + + + Kim Bieler Graphic Design www.kbgd.com + + + + + + + + + + + + + + + + + + ________________________________________________________________ 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
