開発者ロードマップ

Overview

In the spirit of openness and transparency, we publish this roadmap to help developers plan for changes that may require code modifications. Like all roadmaps, it may shift slightly, but we will share insight into what is happening as details become available.

We encourage developers to subscribe to our blog, where we announce rollout plans and timing. If you have questions about these changes, please share them in the Developer Forum.


Canvas and Page Tabs

Item Timing Description
Support for iframes in Page tabs Live New method for using iframes in Page tabs
No new FBML apps March 11, 2011 We will stop allowing new FBML apps, but will continue to support existing FBML tabs and apps. Instead, we recommend using iframes.
All iframes using POST March 12, 2011 Apps can test now by enabling in the Developer App, under Advanced settings > POST for Canvas. FBML apps using preload FQL will continue to work.

Deprecations

Item Timing Description
Old REST API methods Removed Some methods are no longer available. See full list
Data storage API Removed This is no longer available.
<fb:editor> Removed This is no longer available.
<fb:wall> Removed This is no longer available.
<fb:feed> Removed This is no longer available.
Old Insights for Pages Removed Now that historical data and date selectors are now available in the new Insights dashboard, the old Insights dashboard has been removed.
Old Test Users February 2011 With the new test user functionality, we will be retiring the old test user accounts.
<fb:board> Q1 2011 This will be no longer supported and will not be available to new apps.
Auth.promotesession Q1 2011 This method is deprecated and will be removed once an alternative is available via OAuth for apps that use Facebook Chat.

Migrations

Item Timing Description
November 2010 Rollup This migration will become default for all new apps on 2010/12/10 and will be automatically enabled for all apps on 2011/02/10. You can test this migration by enabling it on the Advanced tab in the Developer Application.
  1. Graph API: The fan_count attribute on the Page object will be renamed to likes.
  2. Graph API: The likes connection on the Post object will include both the count and the users that have liked the object.
  3. Graph API: All id fields returned by POST calls will be typed as strings.
  4. FQL: The networks field in privacy table will be 'ALL_NETWORKS' instead of '1' if an object is shared for all of user's networks.
約1週間前に更新