Delaying call to require_login for accessing Facebook applications: Benefits, How-To and Case Studies

9,585 views

Published on

Why you should defer the call of require_login() in the Facebook applications you build as far as possible.

Published in: Technology, Design
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
9,585
On SlideShare
0
From Embeds
0
Number of Embeds
664
Actions
Shares
0
Downloads
36
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide

Delaying call to require_login for accessing Facebook applications: Benefits, How-To and Case Studies

  1. 1. Nitesh Nandy www.mobicules.com <ul><ul><li>Delaying user login for accessing Facebook applications: Benefits, How-To and Case Studies </li></ul></ul>
  2. 2. require_login() - Why <ul><li>With require_login(), the application takes the user's permission to access her personal data stored with Facebook. </li></ul><ul><li>An application page can be made available to a user without her having given permission to it to access her data, if require_login() is not called on the page. </li></ul><ul><li>Such pages are accessible even without the user having logged into Facebook! </li></ul>
  3. 3. Example
  4. 4. Why delay require_login()‏ <ul><li>Application Preview </li></ul><ul><li>Search Engine Optimization </li></ul><ul><li>Being in Facebook's good books (Feed Ranks)‏ </li></ul><ul><li>Better User Experience </li></ul>
  5. 5. Application Preview <ul><li>Seamless transition into the application </li></ul><ul><li>Let the users taste your application before adding it </li></ul><ul><li>Easier for bloggers to write about apps and link to them on their blogs </li></ul>
  6. 6. Feed Rankings <ul><li>The probability of a feed story showing up on a friends homepage who has not added the application depends on the 'quality' of feeds. </li></ul><ul><li>Facebook analyzes the user's click-stream after clicking on a link from the story to estimate the 'quality'. </li></ul><ul><ul><li>Whether the link forces an application Allow Access </li></ul></ul><ul><ul><li>Time spent on the landing page from the feed </li></ul></ul><ul><ul><li>Users marking the feed as irrelevent </li></ul></ul>
  7. 7. Feed Ranking <ul><li>Delaying require_login() helps show the user a landing page which has relevant content. </li></ul><ul><li>Better Feed Rankings --> Better Viral Growth </li></ul>BAD good
  8. 8. Search Engine Optimization <ul><li>Important user acquisition strategy apart from viral channels </li></ul>
  9. 9. Search Engine Optimization <ul><li>Crawlers do not login to facebook and install apps </li></ul><ul><li>Serve pages without requiring logins </li></ul><ul><li>Apps are served from apps.facebook.com so apps get to ride on back on facebook’s page rank </li></ul><ul><li>Serve XML Sitemaps off apps.facebook.com and notify search engines about changes on your application </li></ul>
  10. 10. Better User Experience <ul><li>Asking to add before allowing to access any content results in bad user experience </li></ul><ul><li>User cannot be expected to grant privileges when they haven’t seen anything on application </li></ul><ul><li>Let the user access the content and then ask for addition </li></ul>
  11. 11. “ Good content easily accessible&quot; <ul><li>Links in feed stories should show the full content before prompting to add </li></ul><ul><li>Content shown before adding should be reasonably authentic </li></ul><ul><li>A good amount of application data should be open for crawler indexing </li></ul>
  12. 12. <ul><li>Thanks </li></ul><ul><li>Nitesh Nandy </li></ul><ul><li>[email_address] </li></ul>

×