Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I've implemented some sites with Facebook Connect. The short answer is yes; it's flaky. Load times can be very long, API calls often fail, images don't load, and there's the awful reality of having to use third-party cookies. The documentation is decent, but often dated. </p> <p>You'll just have to weigh the gains you get (huge community, really cool cross-pollination, template posting, friend-linking) versus the headaches of being a Facebook developer. The platform is super young though, and it'll be worth it to implement in the long run. I wouldn't recommend replacing a traditional user/pass system completely right now, but it's great for linking accounts and posting "wall posts" to user feeds (which is pretty easy to implement).</p> <p>One of my biggest gripes with Facebook development is that you have to create <em>new</em> applications for every environment. Have a local server? Application. Have a development server? Application. The live server? Another application. Each is tied to a base domain, and there's no way to add multiple domains (though sub-domains work). You have to configure each application for each environment. Also, the fact that you can't "edit" wall templates is tough as well; you have to delete and start over as far as I know (even if you just want to correct spelling or something).</p> <p>It's weird. Some aspects of Facebook development are an absolute <strong>joy</strong> to work with. And some are the worst development experiences I've had.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload