- January 1, 2012: FBML will no longer be supported. We will not fix FBML bugs after this date with the exception of security and privacy issues
- June 1, 2012: FBML apps will no longer work on Facebook. All FBML endpoints will be removed.
We realize that some of you may still be relying on FBML for your apps. We want to make sure that you have all the resources you need for an easy and speedy migration. Over the past few months, we’ve been working with developers to understand the remaining use cases for FBML. Based on these conversations, we identified two primary use cases remaining: Requests and Static FBML tabs on Pages.
We have already announced the new and improved Request 2.0 which should make migrating from FBML Request much simpler. To upgrade to Requests 2.0, apps should send requests by using the Request Dialog. To learn more about Requests 2.0 and how to migrate from FBML Requests, see our documentation on Requests.
Custom tabs on Pages are an important aspect of Facebook Platform. Many developers and Page admins rely on Static FBML for hosting this content. With the deprecation of FBML, this content must be moved to an iFrame based solution. There are several free iFrame solutions available that allow easy migrate Static FBML content to HTML. The Preferred Developer Consultant Finder on Facebook is a great tool to find PDCs to help guide you through the upgrade process. In addition, we have worked with WildFire, one of these PDCs, to create a step by step tutorial to guide your migration. The tutorial is available here.
We are excited to move into a modern, standards based Platform. Please provide feedback and thoughts in the comments below.