| My experience with building an alternative Android Facebook client (which naturally uses almost every part of the API): 1) Just keeping up with documented and undocumented breaking changes is probably a full time job. 2) Expect that some feature of the API breaks every 2 weeks, especially login on their Android SDKs cannot be relied upon.(reliable for me is the industry standard for server uptime usually advertised - 99.99999%) If your application just uses few parts of the API it probably once every 1 or 2 months. 3) Substract 0.5 to 1.0 points from the rating of your app in the Android or iOS app store, depending on how heavy you rely on Facebook, because of the instability of their APIs. 4) Expect to spend at least a day per month writing bug reports. (Or just give up like I did) 5) You will do lots of reverse engineering to work around the bugs which they are constantly creating at a mind blowing rate. My final conclusion after almost 2 years of working with their APIs (as a good actor) for my app (link: https://play.google.com/store/apps/details?id=com.flipster&h...) is that I will never ever ever build again something that relies that much on Facebook. If I need a friends list in a future project, I'll just use the users telephone book, like I already did on a VoIP/Messaging app for mobile that I built for the company I work for. If I need private messaging I'll just set up my own XMPP server. If I need login, I will sure as hell save myself the headache of using their fucked up (and even when it is working - bad converting) login, and build one myself! |