In an earlier post, I detailed some important differences between version 2.0 of Facebook’s graph API and the old version. These include the replacement of global user ids with application-specific ids, and the new restriction of friend data to friends that have connected to the client application. If you’re not familiar with these differences but would like to read on, I recommend reading that post first. In this post, I turn my attention to building features with the restricted data that v2.0 affords us. I will walk through three related features:
- Finding your users’ Facebook friends who are already using your app.
- Notifying existing users of your app when their Facebook friends register.
- Allowing existing users to invite their Facebook friends to join.
Find Your Friends
One common use case for integrating with Facebook is to allow users of your application to find friends who have already signed up. This kind of feature can allow new social platforms to bootstrap community by making use of the connections its users have already formed on Facebook.
The first step is to collect the data that will enable your app to make these connections.
When a user connects to Facebook via your application, you should store the Facebook id for that user.
When the time comes to search for Facebook friends, make a call to
user/friends, and cross reference the returned user ids with the ones in your database.
Keep in mind that in the new version of the API, you’ll only get back friends who have previously connected to your application. If a user has a Facebook friend who signed up for your service but never connected via Facebook, you will not be able to connect the two of them. You cannot, for instance, retrieve the email addresses of a user’s freinds.
This sounds simple enough, but there’s an obvious worry here. When I recently built a feature like this, I had a moment of terror. The webiste I was working on had been storing Facebook ids for years, but had been doing so under the v1.0 scheme. That meant that all of the ids we’d stored were global ids. But now we were upgrading to v2.0, and v2.0 returns app-specific ids. There is no way to map app-specific ids to global ids; the whole idea of the restrictions imposed by the new API is to prevent applications from sharing information about users. So how would I ever be able to match up users with their friends?
It turns out that this is a non-issue. However, to figure that out you need to find the following sentence, which is burried in the Facebook developer docs:
No matter what version they originally used to sign up for your app, the ID will remain the same for people who have already logged into your app.
In other words, existing v1.0 users of your app get grandfathered in and are still returned from API calls with global ids. All of those ids stored in the database are still useful for cross-referencing. Phew!
Get Notified when Friends Sign Up
After a user has found their existing friends in your application, you may want to inform them when other Facebook friends sign up.
This can also be accomplished using the
When a user connects via Facebook, retrieve their (application-scoped) friends, and match their ids up with those in your databse.
You can notify the matched users as you see fit.
Invite Your Friends to Join
Let me explain.
We cannot use the
user/friends endpoint to find friends for a user to invite, because the only friends it will return are friends who’ve connected already, and there’s no point in inviting someone to a party they’re already at.
There are two endpoints of the new Graph API that will return information about all of a user’s friends:
The latter is retricted for use by Facebook games, and so in general,
taggable_friends is your only option for retrieving a list of all of a user’s friends.
taggable_friends only provides full names, thumbnail profile pictures, and an identifier that’s only usable for tagging people in stories published on Facebook.
There is no way to retrieve any kind of useful identifying information, such as a Facebook id (either global or app-specific), an email address, or a Facebook username.
The send dialog requires a Facebook id or username to identify a recipient.
Therefore, it’s impossible to build an ‘Invite’ button that brings up a Facebook message dialog with recipients pre-filled.
1 2 3 4
If you like, you can inspire your users to invite their friends by showing them profile pictures retrieved from
Here’s an mock-up of a feature like that (as designed by Ryan and Ryan):
This generic invite functionality is easy to build, and probably nicer for your users than providing the ability to sift through hundreds of Facebook friends.