We’re excited that developers are beginning to realize the power of integrating Facebook into their mobile apps. As of today, seven of the top 10 grossing iOS apps and five of the top 10 Android apps have integrated with Facebook.

Facebook sends over 160 million people to mobile apps each month through news feed and timeline. Soon, with the App Center, it will be easier than ever to drive mobile app installs and reach the over 500 million people using Facebook on mobile devices.

Installing apps from a mobile device
People will be able to access the App Center from Facebook’s iOS app, Android app and m.facebook.com. After someone clicks the install button on your mobile app detail page, they’ll be logged in and redirected to your app.

If someone already installed your native app, we automatically open your app, passing in an access token for the authenticated user. If they haven’t, we immediately show the user the install page in the Apple App Store or Google Play.

When someone installs your mobile web app, we redirect them to your mobile URL. As a reminder, all mobile web apps need to call 'FB.getLoginStatus' and show a personalized experience to be listed in the App Center.

Installing apps from a computer
We’ve also built a convenient mobile install flow for people browsing the App Center on their computer. All apps built for iOS, Android, and the mobile web have a “Send to Mobile” button on their app detail page.

Once people click “Send to Mobile,” they’re logged into your app and we immediately send a Facebook notification to their mobile device. By clicking the notification, they’ll be redirected to your mobile web app or the respective install page in the Apple App Store or Google Play.

Include your mobile app
All mobile apps with Facebook Login are eligible to be listed in the App Center. For more information, see the step-by-step documentation and sample code available in the iOS Getting Started and Android Getting Started guides.

You’ll also need to create an app detail page in the Developer App. Learn more about creating a page and the guidelines.

We’re looking forward to helping people find and install more mobile apps with the App Center. It’s not too late to include your mobile app in the launch, so make sure you integrate Facebook Login and create your app detail page.

Tumblr is a blogging platform that lets people post content – including images, videos, links and audio – to their tumblelog, a short-form blog. Tumblr integrated Open Graph into their web and mobile apps to make it easy for people to post Tumblr content to their timelines.

Tumblr web app

Tumblr mobile app

What Tumblr Does Well

Tumblr associates a photo with each post published to timeline and news feed, creating more attractive stories for friends. Tumblr uses the message property for personal messages on the Post, Reblog and Reply actions to show more relevant content to friends.
Tumblr provides clear messaging about what activity is posted to timeline and simple controls to help users determine what is shared on Facebook.

Implementation Profile

Actions - Objects Post - Entry, Photo, Photoset, Video, Audio, Link, Quote, Conversation: "Jeff Sherlock posted an entry" Reblog - Entry, Photo, Photoset, Video, Audio, Link, Quote, Conversation: "Chris Ackermann reblogged a photo" Like - Entry, Photo, Photoset, Video, Audio, Link, Quote, Conversation: "Andy Mitchell liked a link" Reply - Entry, Photo, Photoset, Video, Audio, Link, Quote, Conversation, Question: "Jillian Stefanki replied to a question"

Aggregations Most Recent Post Likes Recent Likes Recent Posts Recent Reblogs

Result
Since launching with Open Graph in April, Tumblr has seen referral traffic from Facebook increase by more than 2.5x.

Since last Wednesday's update, we published a Developer Spotlight on Endomondo, announced the Action Spec Preview Tool, published Monitoring App Quality with Insights, and we published App Center Best Practices.

Updates on the Javascript SDK

In the upcoming weeks, we will be updating the Javascript SDK to limit the publicly exposed interface. This is part of an ongoing process to improve the reliability of the SDK. The first step will include removing access to all internal properties and to methods prefixed with _.

If you are applying patches to the FB object, these will no longer take effect, nor will directly manipulating properties such as FB._https. If you are currently relying on accessing internal properties, please refactor this so that you only rely on the publicly available (and officially supported) methods listed at https://developers.facebook.com/docs/reference/javascript/.

Note that all methods not listed as part of the public API might be subject to change or removal, and you should not use them directly.

Breaking Changes Effective on June 6, 2012

As announced on the Roadmap and Developer Blog, on June 6, 2012, the following changes will be in effect:

Removal of FBML
FBML apps will no longer work on Platform. All FBML endpoints will be removed. If your app is still utilizing FBML, please migrate before June 6 to avoid any issues.

XMPP Connections must be done over TLS
Apps connecting to Facebook's XMPP service will be required to use STARTTLS for all connections. We will start rejecting unencrypted connections.

Bugs activity between Tuesday, May 8 and Tuesday, May 15

• 174 bugs were reported
• 27 bugs were reproducible and accepted (after duplicates removed)
• 12 bugs were by design
• 48 bugs were fixed
• 49 bugs were duplicate, invalid, or need more information

Bugs fixed between Tuesday, May 8 and Tuesday, May 15

• submit repro form failed
• Uncaught Error: No polyfill registered for object connect.facebook.net/en_US/all.js:24
• Login-button not displaying for users logged into FB.com
• Applications fail to load du to currupted jS script (Uncaught SyntaxError: Unexpected token ILLEGAL)
• Insights for my app not updating since 5/7/2012
• parse is not defined in FB.JSON.parse
• Submitting a post request to https://graph.facebook.com/<page_id>/photos returns "An unexpected error has occurred. Please retry your request later."
• Open graph action approved but still shows "pending"
• Facebook Like comment overlay has z-order problems in IE compatibility view
• Recommendation plugin does not display any recommendations
• Application authentication error when uploading picture to ALBUM created using web application
• Used gift notification URLs point to Apps and Games rather than app
• Request Dialogs broken in IE9
• Impossible to publish links on Facebook
• FQL : some type values are not documented on STREAM table
• The user_checkins and friends_checkins is not asked when someone want to install my app.
• Timeline's milestones not appearing in graph api's feed or fql results
• Broken link to "Post object" on stream.publish deprecation note
• page_fans/lifetime shows zero for some days
• Posting on event using graph api is not work as its need to work
• Auth'd user cannot create video.watches action.
• Cannot connect "read" action to built-in object type of "book"
• NULL FQL impressions field since 12/15, and post insights completely missing
• Auth Dialog Form: Tooltip and text box for Headline don't agree.
• Failed to Create new action for a recreated App
• Search API not returning new results
• Watch Action Type is busted
• /me/cover brings an oauth (fql?) failure
• Having major problems writing actions to open graph after possible GDP / permissions / auth change
• Number of Likes from Insights API does not match Graph API or Page itself
• Facebook Page Tab Application with top.location.href containing a URI fragment fails to re-load when you "LIKE" or "UNLIKE" the page
• FB.Canvas.getPageInfo() callback not being called in HTTPS
• FB footer below fluid canvas is too tall, needs cleaning up.
• use_online_presence always returning 'offline' status
• Insights Auth Dialog data incorrect
• result of get order id is different from documentation
• Offers callbacks are not populating the "data" field
• Timezone less events - Twitter Bug
• Can't make Graph API calls on test users when using their auth tokens
• Bug: Platform Policies Contact Us Link
• Specific event name fails
• Facebook Invite hangs for an user with about 4000 friends
• Developer App will not allow "localhost" as App Domain
• Missing posts in wall post feed
• OG:image changes not being reflected in the Graph
• Issues with Credits processing
• Graph API photo upload to fanpage returns unknown error for specific images
• RFE: No way to cancel a bug submission

Activity on facebook.stackoverflow.com between Tuesday, May 8 and Tuesday, May 15

• 477 questions asked
• 405 questions with a score of 0 or greater
• 146 answered, 36% answered rate
• 244 replied, 60% reply rate

Last week, we announced the App Center, a new channel to grow canvas, mobile, and web apps that integrate Facebook. We encourage all developers to submit their app detail page this week. Having an app detail page is required for being listed in the App Center, and it will also become the new destination when non-users search for your app.

We are already reviewing app detail pages for apps that have high enough quality signals to be listed in the App Center. We are impressed with the quality and number of submissions to date. Checkout the impressive app detail pages created by Zuma Blitz, Soundcloud, and Pulse.

We published the App Center guidelines to help you understand what we expect of apps that are listed. In addition, the below checklist highlights some of the most important things to consider when you’re creating your app detail page:

1.) Websites must provide a personalized experience.
When people click through from the App Center, they are logging into your website. As a result, do not present these users with “Login with Facebook” buttons.

All websites and mobile web apps need to immediately present authenticated users with a logged-in experience. Specifically, we’re looking for personalization, such as name and profile picture, so users know that their Facebook information is being used to create an account.

One of the easiest ways to detect user status is to use the JavaScript SDK and the FB.getLoginStatus call on your landing pages. Learn more.

2.) Review your app settings.
App detail pages are dynamic based on the integrations you’ve specified on the basic settings page of the Developer App. Be sure to review this and remove any old or non-functional integrations. If you don't use Facebook Login on your website, please don't list it.

For example, if you’re building only an iOS app you shouldn’t have anything in the Site URL, Mobile Web URL or Canvas URL fields.

3.) Provide high-quality images.
Your images should match the quality of your app. As specified in the guidelines, images shouldn’t have buttons, excessive text, borders, dropshadows, URLs, promotions, pricing, or third-party logos.

Icons and promotional banners cannot have a white background, rounded edges or borders. If your logo has rounded corners, please fill the white space in the corners with a color. Also, all promotional banners must include the name of your app.

Screenshots should be screenshots of the actual experience (no additional graphics overlaid, no distorted angles). Feel free to use concept art in your cover image and icons, but please keep it out of screenshots.

4.) Input accurate names & thoughtful descriptions.
Don’t add any additional keywords to the name of your app. For example, if your app is named “Billiards”, don’t submit your name as “Billiards – Pool”.

Proofread your app description for spelling and grammar and remove unnecessary symbols, like stars, hearts and multiple exclamation points.

5.) Don’t forget to save and submit.
We understand that it may take some time to create a great app detail page, so we provide the ability to save your work before submitting. Once you’re done, don’t forget to click the “submit” button at the top of the page.

In the coming weeks, we will be providing additional information about how the localization and translation process will work for app detail pages.

As a reminder, all app detail pages submitted by May 18th will be given prioritized review for the user launch of the App Center. If you haven’t already, create your app detail page today.