Great pattern -- I'd like to see it include an additional guideline. Not only should you "return them to the context they were in when they were about to comment" but take additional steps to preserve this context even if there are problems during the sign-in process. I've seen plenty of apps that get the first part right, but assume a seamless, error-free login. Then they have some semi-hard-coded "Return to top of site" behavior as a generic catchall action from the Sign-in Error page. T-mobile, I'm looking in your direction…
-- Bryce
Sign-in Continuity
Bryce23 Sep 2008 9:50 AM
Amber C.23 Sep 2008 11:59 AM
Bryce, I agree with you very much on this point;
I'd also add an additional point:
* The sign in flow should take the least amount of steps necessary to the user. Reduce click liability by providing the most used functions first, with options for second used functions directly below. Don't make the user click to sign in - provide the box already, and if the user fails twice, turn the sign in box into an E-mail prompt for lost password while retaining the "sign-up" option the entire time.
QUOTE (Bryce @ Sep 23 2008, 08:50 AM) <{POST_SNAPBACK}>
"return them to the context they were in when they were about to comment" but take additional steps to preserve this context even if there are problems during the sign-in process.
I'd also add an additional point:
* The sign in flow should take the least amount of steps necessary to the user. Reduce click liability by providing the most used functions first, with options for second used functions directly below. Don't make the user click to sign in - provide the box already, and if the user fails twice, turn the sign in box into an E-mail prompt for lost password while retaining the "sign-up" option the entire time.
xian6 Nov 2008 1:29 PM
These are both excellent suggestions. I plan to review and update the pattern to address these comments.
QUOTE (caseorganic @ Sep 23 2008, 10:59 AM) <{POST_SNAPBACK}>
Bryce, I agree with you very much on this point;
I'd also add an additional point:
* The sign in flow should take the least amount of steps necessary to the user. Reduce click liability by providing the most used functions first, with options for second used functions directly below. Don't make the user click to sign in - provide the box already, and if the user fails twice, turn the sign in box into an E-mail prompt for lost password while retaining the "sign-up" option the entire time.