HTML and CSS Reference
In-Depth Information
"education": [
{
"school": {
"id": "107993102567513",
"name": "Whitefish High School"
},
"year": {
"id": "194603703904595",
"name": "2003"
},
"type": "High School"
}
],
"gender": "male",
"email": "jason\u0040lengstorf.com",
"timezone": -7,
"locale": "en_US",
"languages": [
{
"id": "113301478683221",
"name": "American English"
}
],
"verified": true,
"updated_time": "2012-06-29T21:53:51+0000"
}
This data can be used within your app to customize the user's experience, identify any actions they make, and
other functions that would require information about the user.
Why OAuth Is Better Than Building a Login System
Using OAuth to authenticate users is, in many cases, a better solution to the “user account” problem. Creating new
accounts is a pain for both developers and users, so when the app doesn't have an explicit need to closely control its
own registration process, there are a lot of good reasons to use OAuth rather than implementing something specific to
your application. Some of the benefits include these:
•
One fewer account registration and password for users to deal with, which lowers the barrier
to entry for potential new users: getting started means three clicks versus filling out a form,
checking their confirmation e-mail, and then logging in.
•
The app has access to basic user info without asking for any additional input or actions from
the user beyond authorization.
•
The app has access to the service provider's API and its benefits (such as sharing a user's app
activity on Facebook, if the permissions allow it).
•
It eliminates the need to build a complex and customized login system, which saves hours of
maintenance and development.
Search WWH ::
Custom Search