- We design and build extraordinary applications for companies looking to make the next great idea a reality.
- learn more
Mashups versus Facebook
I've been playing around with the Facebook API over the last few weeks. There's only a very limited Ajax capability in the API -- they call it "Mock Ajax" -- that allows you to sub some very restricted HTML into the innerHTML of DOM elements. No Javascript. You'll have to use inline CSS if you want to achieve a cool user experience.
While it is possible to display Facebook content in your own apps, it is pretty restricted (you'll have to read at least three legal docs to figure all that out). Not much leverage for mashups here. In a sense this is the mirror opposite of a mashup. Instead of mashing together services provided by third party, you develop a service that is mashed into the Facebook platform.
Part of the promise of Ajax was that you could mash together third party services quickly and comparatively easily. While widgets and services have made their mark (Yahoo, Flickr, Google Maps to name just a few), there is also a trend toward restricting their use. See the discontinuation of the Google SOAP Search API and the heavy restrictions on the new Google Ajax Search API. Right now my money is on the Facebook model winning out over the Mashup model.
BTW, in exploring the Facebook API, I experienced a flashback to the late 90's and the whole portal fad. The API's and patterns reminded me more than a little bit of Plumtree and Epicentric (great portal platform before it was absorbed into the craptastic Vignette). What's old is new again, just like bell bottoms and mood rings. Just don't call facebook a portal.
Technorati Tags: ajax, facebook, portal, mashup
Topics: Mashups
Comments: 2 so far
Leave a comment
About Pathfinder
Recent
- Roles Testing For Security
- Blackbird takes the pain out of JavaScript logging
- Making GWT JSON not Quite so Painful
- IDEA - preconference workshop 06 Oct 08
- HTML5, Ajax history management, and The Ajax Experience 2008 Boston
- A Look Back At Past Posts
- Flash Player on iPhone gossip
- Microsoft to Jump on Board EC2
- TAE Boston 2008: The Unsexy Presentations
- The Ajax Experience 2008: Hope to see you in Beantown
Archives
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
- September 2007
- August 2007
- July 2007
- June 2007
- May 2007
- April 2007
- March 2007
- February 2007
- January 2007
- December 2006
- November 2006
- October 2006
- September 2006
- August 2006
- July 2006
- June 2006
- May 2006
- April 2006
- March 2006


A true facebook widget is written in actionscript. That’s the only way to get to their apis from the client. Javascript would cause too many security issues. The Facebook markup language (FMBL) makes it seem that they support various languages like C# .net etc, but it does nothing but add complexity to a system that has only one true way to build a dynamic widget.
Comment by Rainhut, Friday, September 7, 2007 @ 11:44 pm
Check out the Stagegold video player as an example of a true widget on facebook.
Comment by Rainhut, Friday, September 7, 2007 @ 11:47 pm