2. In an ideal world...
The user understands...
▪
the value of single sign in.
▪
the relationship between RP and OP
▪
What parts of their identity are being shared
▪
They understand all this without being overwhelmed by choice and
complexity
Tuesday, February 10, 2009
4. How can the user understand the value?
Value: Skip filling out this
▪
form or registering if you have
a Facebook account
Problems: this experience is
controlled by the RP.
Solutions:
Education - team works with
outside parties to provide
guidelines, design tips, and best
practices.
Brand - Facebook icon,
distinctive distinctive blue button
Tuesday, February 10, 2009
5. The problem of choice
Citysearch solution
▪
isn’t really scalable to a
bunch of dierent
provider.
At the same time, you
▪
don’t want to present
too many choices.
What is the happy
▪
medium?
Users respond to
▪
brands, not concepts.
Can we limit options
▪
by being smart?
Tuesday, February 10, 2009
6. What is the relationship between RP and
Problem: we want to message
▪
“Hey, these two sites are
going to be tied together
somehow.”
Solutions:
Simple popup - don’t get taken
away from the RP
Graphics - both RP and OP are
portrayed with their logos.
Simplify everything else--not
much text, since users tend not
to read.
Tuesday, February 10, 2009
8. What’s being shared?
Problem: we want the user to
▪
understand that connecting
means RP will know who they
are, and can publish stu back
to Facebook.
Solutions:
Arrows - indicate what data is being
transferred in each direction
Profile picture - shows up on 3rd
party site.
Simplify - additional permissions
granted later as needed.
Tuesday, February 10, 2009
10. As a community...
▪ We need to figure out how to sell the value of a
single identity on the web
▪ We need to provide a simple, standardized
authentication experience
Tuesday, February 10, 2009
11. Selling the value
Where should the integration begin?
▪
With log in?
▪
With registration?
▪
How should it be worded?
▪
“Use OpenID...”
▪
“Sign on with your ____ account?”
▪
What graphics or buttons should be used?
▪
Deliverables: provide a list of guidelines and best practices for
▪
the sign on experience
Tuesday, February 10, 2009
13. The Auth Experience
Can we simplify?
▪
Can we standardize?
▪
▪
Tuesday, February 10, 2009
14. (c) 2007 Facebook, Inc. or its licensors. quot;Facebookquot; is a registered trademark of Facebook, Inc.. All rights reserved. 1.0
Tuesday, February 10, 2009
