Showing posts with label api. Show all posts
Showing posts with label api. Show all posts

Monday, 26 April 2010

The end of web destinations - Facebook Open Graph slideshare deck

It doesn't seem too much of an overstatement to suggest that Facebook's Open Graph protocols have created a new OS for the internet: one that is based more on how people interact with each other than on how they relate to entertainment content. There are obviously huge issues around several of the announcements from f8 last week, centering on three subjects

Privacy (Marshall Kirkpatrick on ReadWriteWeb)
Advertising value (The Ad Contrarian on Facebook's Nielsen partnership)
(and linked to that...)
Whether Facebook can match the attention that they are gathering with a similar level of profit (Henry Blodget in Business Insider)

All three are well worth a read if you are interested in Open Graph. And if you work with brands and the internet, you are interested in Open Graph aren't you? Personally I think that Facebook has created a product with incredible potential, that will increase its revenue (although not yet up to Google level; they need another killer app for that, which i think they'll find next year) and make people's experience on the internet better. Privacy is increasingly something people are willing to trade for better. Ethically I think we're getting a bit hysterical about things, mainly because Facebook have a slightly dubious record in privacy isues, but also because they are starting to close in on Google, who are genuinely ethical in a way that few bigh corporations can be. Let's face it, they are a business who have improved what they do in order to be more profitable.
Anyway, I've been thinking a bit about how Open Graph changes things. To be honest, the stuff in the deck was all possible with Facebook Connect if it was used in full, but very few brands were doing that. I'm not a developer so I don't know how difficult it was to implement, but by all accounts Open Graph is a whole lot easier. I'm going to follow this up once there are more distributed nodes in the graph (ie more people liking more content and more sites implementing personalised social features) and look more at the content side of the protocol.

For now this is all about how the APIs are starting to become an alternative to the web destinations of old. In order to take full advantage of all the combined benefits of the networks available to a brand, we need to start thinking about whether people have a temporary high interest in the brand, or a permanent loose interest.
Then about how we move them around according to their needs and attention. And if we are going to require them to move around, how we are going to inspire them to participate. Ironically considering Facebook's change in terminology, we need to think about how we make them a fan (in the real sense of the word- not just saying they like something on a social network).

It's very early days for Open Graph, so I'd really welcome your thoughts on this deck in the comments or on Twitter

Tuesday, 11 November 2008

The information democracy hits old media

The New York Times has released three APIs in the last month. No, I didn't hear about it either. Doesn't even register when you search on Guardian Media, but it is a far bigger step to freeing information from the traditional publishers' archives than the Guardian's move to publish full text RSS last month.

Campaign Finance API app


Why is this? Because of what an API (Application Programming Interface) allows thrird party developers to do. As an example, the most famous APIs are those of Facebook and Google Maps. They are the code that allows content to be remixed, mashed up, passed on, and generally made useful for people.

And why so important for developers? To use an example from Adam Broitman's article for MIN Online:

Say you are a movie buff who decided to create an amateur movie review site. Along with every one of your reviews you want to include one of The New York Time’s 22,000 movie reviews (dating back to 1924). In theory (as there are rules that govern the use of the API) you can build an application that automatically pulls the movie review, and all information that The New York Times has on the movie you are reviewing, into a format that you designed for presentation on your site.

And why so important for traditional publishers? Well, we don't really know yet, as there's no subscription cost, and obvious source of ad revenue. What is really important is that this information used to be hidden away in a destination site, and is now free to move around wherever developers' imaginations take it. Say the example above takes off, then the NYT's reputation will grow as the reference point for online movie reviews. We don't know how the future revenue model of the internet will work, but you can be fairly sure that money will follow reputation.

Do we think the UK tech/media press missed this as they didn't think it was significant?