I've done some facebook functionality for our company (some quite simple stuff). The API is quite stable, and what I worked on works almost two and a half years later. Facebook does change the API, but there is a period of time to adapt, and it usually is backwards compatible. So what changes did affect me, were not huge. I had the advantage of implementing it in a browser environment of sorts (xul application).
Existence is pain
It seems my concerns are unfounded in the present day, if it's not an issue any more then it should be safe to ignore my recommendations.
But for those reading, abstracting your interfaces (in this example, creating a 'man in the middle' between your code and 3rd party API) is a good idea when you can't be sure of the stability of the 3rd party API or if there's a chance you'll switch to a completely different API.
When the moon hits your eye like a big pizza pie - that's an extinction level impact event.
Reply With Quote
Bookmarks