On Dec 13, 2007 2:31 PM, Brian Moseley <[EMAIL PROTECTED]> wrote: > On Dec 13, 2007 11:25 AM, hank williams <[EMAIL PROTECTED]> wrote: > > > I was speaking in general terms, not in the case of chandler. Often > > there is a choice as to whether to ask for sign up information in a > > webapp and it is often best to defer because of the drop off dynamics, > > until the user has more invested. > > right. I just wonder about the application of this principle to > Chandler. it seems like once a user has gotten to the point where he > wants to sync his data or share some information so that it can be > accessed on the web by somebody else, he needs to shift to the frame > of mind that allows him to provide some details to the server. how > best to do this so that it's not off-putting to the user but still at > least somewhat secure (the reason for account activation), I'm not > sure. > > _ _ _ _ _ _ _ _ _
Yeah, just to clarify, I was speaking in general terms, and I agree that doing this with chandler is really not possible. Though I do think that making one screen where the user doesnt have to go to the website is a good thing. The account should immediately be created, and the activation email should be sent but the account should be good for like 24 hours before it times out if the activation email link has not been clicked on. Hank _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
