Facebook Adds Graph API, OAuth 2.0 Integration to iOS SDK

The iPhone SDK, renamed the iOS SDK to match Apple’s mobile operating system name change, has a couple new product updates. One is that developers can now integrate the Graph API with their apps, allowing for simpler connections from mobile to a wide range of Facebook data. The other addition is that they will be able to use Oauth 2.0 authentication technology, a standard for secure two-way user data transfer.

Facebook already introduced both of these features at its f8 developer conference in April, but had not yet made them available for iOS developers. The point of the API is to create a simpler and more consistent framework for third parties to access Facebook data, showing each piece of Facebook data – people, photos, Pages and events — as an object in the API, along with the connections between them, including friend relationships, and photo tags and shared content.

The addition of the Graph API today means iOS developers can more easily integrate Facebook features. The code base is “smaller, cleaner, and just has a few functions,” Facebook platform engineer Luke Shepard tells us. “From most developers’ perspectives, it is now simpler to do.”

The impact could be subtle, but still big. If more developers start connecting to Facebook objects like photos or events, and get more two-way communication going between the mobile product and Facebook, that could lead to more app discovery, and revenue. Mobile social applications have so far been taking awhile to evolve, partly because mobile platforms themselves have not yet developed compelling ways for people to create social identities and share information around apps. Simpler social features could mean Facebook users might start seeing more stories being shared about their friends iOS app activities, leading them to click through and check out the apps on their mobile devices.

Making itself useful to mobile developers has been a big priority for Facebook in the past couple years. The first version of the iOS SDK launched more than a year ago, and has slowly gained features. Facebook has also been busy on the main smartphone OS alternative to Apple, Google’s Android — Facebook pushed out the Graph API and Oauth 2.0 update to its Android SDK in May, when it also introduced the feed publishing option.

Tumblr Marketing

Mediabistro Course

Tumblr Marketing

Starting December 1, learn how to market using the most popular visual blog! In this course, you’ll learn how to develop a strategy for your own Tumblr account, get people to read and share your content, and integrate your marketing efforts with other social platforms. Register now!

 

Leave a Reply

4 Responses to “Facebook Adds Graph API, OAuth 2.0 Integration to iOS SDK”

  1. News codice n.1 says:

    [...] that takes minutes, not hours to experience.” Sell Simply sellers have a Simple more… Facebook Adds Graph API, OAuth 2.0 Integration to iOS SDK – Inside Facebook (blog) – insidefacebook.com 08/12/2010 Facebook Adds Graph API, OAuth 2.0 Integration to iOS [...]

  2. parul says:

    To give you truly worldwide coverage and interoperability, Gateway4SMS has agreements with mobile operators in over 200 countries. We offer you enhanced solutions and easy integration in utilising mobile messaging services in your marketing and communication efforts.With the emergence of mobile marketing, we can help drive and generate new revenue streams for you as customers are demanding more quality mobile data services that are easy to access and deploy with speed, worldwide

  3. Facebook iPhone SDK Adds Graph API and OAuth 2.0 says:

    [...] via InsideFacebook, iPhone screenshot by Phil Hawksworth Related ProgrammableWeb ResourcesLearn more Facebook API Profile [...]

  4. Syberglitch says:

    I have downloaded this SDK and I must say that it has memory leaks and overhead all over the place.
    Common guys having property like
    @property(nonatomic, copy) NSString* httpMethod;
    and in convenient constructor of FBRequest to use setter of that property like
    request.httpMethod = [httpMethod retain];
    that is really bad.
    These kind of things you have all over the place.
    Not to mention constructiopns like
    SomeClass* class = [[[[SomeClass alloc] initWithSomethin:x] autorelease] retain];
    What is the purpose of that. Why not just
    SomeClass* class = [[SomeClass alloc] initWithSomethin:x];
    as outcome is the same. With your construction you just create an instance label it for autorelease pool and then retain it so I really would like to here the reason for these.
    So I think this should be removed from git repository until its totally fixed as it will produce a lot of bad cases for developers who use this.

Get the latest news in your inbox
interested in advertising with inside facebook?

Social Media Jobs
of the Day

Advertising Campaign Manager

Amazon
New York, NY

Web Content Specialist

Philadelphia College of Osteopathic Medicine
Atlanta, GA

Web Producer

InvestmentNews
New York, NY

Featured Company

Join leading companies like this one and recruit from the nation's top media job seekers on the Mediabistro Job Board. Every job post comes with our satisfaction guarantee. Learn More
 

Our Sponsors

Mediabistro A division of Prometheus Global Media home | site map | advertising/sponsorships | careers | contact us | help courses | browse jobs | freelancers | content | member benefits | reprints & permissions terms of use | privacy policy Copyright © 2014 Mediabistro Inc. call (212) 389-2000 or email us