The number two issue is they change the API and don't announce the changes until people start posting questions asking why something is failing.

Number three is random failures with no error. (Did they change the API again or is it just a random recurring event?)

Let me publicly say something I've said privately: I will pay up to $1000/year for a subscription to a service that 1) documents the facebook APIs, 2) monitors examples and common usages and lets me know when they stop working, and 3) provides a weather report for the Facebook API servers letting me know when they're slow or sick.

Heck, I might pay more. We waste far too much developer time dealing with the problems Jobu so rightly points out.

There's a certain lack of clarity and even when you can figure it out some of their decisions are strange. There's barely anything on performance and caching and overall they appear to have geared the API more towards the copy-paste plugin generators they have. I've never seen a 3rd party FB app (apart from the one linked on this page, Clarity I think, which I've only just heard of), and all the Android ones I came across were just site specific browsers wrapping the mobile page.

Compare it to Twitter, which has supported countless apps on practically any platform you can think of and appears to have actually considered a developer will use it. It's nicely laid out and appears to have proper thought put into it.

What really frustrates me is that there are some places in which options exist but simply aren't documented, and in other cases the various call options are listed but with no explanation, so you have no clue what each option actually does for you.