Friday, January 21, 2011

Integrating Facebook social apps into your website puts you at the mercy of Facebook

Some time ago we did a web site redesign. As part of the redesign we decided to incorporate a Facebook fanbox on the home page. We enabled streaming in the Facebook Fanbox so that anything posted on the organization's Facebook page wall would also appear on the homepage. While I was not deeply involved in that part of the decision making, I believe the idea was to keep things fresh and interesting on the home page and increase traffic between the organization's Facebook presence and web site. Mysteriously today the Facebook stream on the home page isn't loading. Empty box. So far no luck in tracking down the problem. Facebook has a developer forum but no formal help system to speak of, and the admittedly small sample of Facebook documentation I've used has been so so.

My experience with Facebook so far has been mixed, and this is one instance of why I don't have particularly warm feelings towards the company. Let me jump back a couple of months. A sister organization of the one I work for, which also has a presence on the same web site, asked me to do a Facebook Fan Box for them as well. When I went to generate the Fan Box code, surprise surprise, Facebook was no longer supporting Fan Boxes. They'd changed them to "Like" Boxes, and what's more they'd removed access to the documentation for Fan Boxes. Indeed it seemed as if the company tried to expunge all references to Fan Boxes. So much for supporting features that they themselves created.

This is apparently what the company means in its user agreement when it says things can change at any time and there is squat the user can do about it. Fair enough. Thing is the only reason Facebook exists is because people and developers use it. When Facebook yanks support for its own features, buries documentation, can't be bothered to help developers track problems, and the like it says to me that I need to be careful in buying in to their system.

No comments: