Back in April, Wired published a story about Yahoo CEO Marissa Mayer's mission to make Flckr awesome again. Likely, that was the motivation behind Yahoo's recent acquisition of IQ Engines, a popular image recognition service.
This week we’re spotlighting the Flickr API, one of our most consistently popular APIs. Flickr is the fourth most used API in our directory appearing in over 600 mashups. Each of the mashups below leverage Flickr and have been named mashup of the day since August.
Something new sprang up in the Flickr App Garden last month: "This is my Cam!" by Chris Martin (the San Francisco-based hacker, not that guy from Coldplay). Inspired by music sharing site This Is My Jam and built during Photo Hack Day 3, "This is my Cam!" uses the Flickr API to catalog the different cameras that were used to capture a particular user's photos.
This week's look at the newest and best mashups will focus on one of the most popular APIs, Flickr. With nearly 600 mashups, Flickr is the fourth most used API in our directory. Each of the mashups below have been added since November and make good use of Flickr.
A competitor created an export tool for Flickr ex-patriots, so the photo sharing site shut down the Flickr API developer key. The Google Plus developer page makes some wonder if the "real" Google Plus API is coming soon. Also: questions about the Google Safe Browsing API, free cloud database and 15 new APIs.
Flickr has added more real-time goodness to their photo API. Using a publish / subscribe (PubSub) system, developers can now receive real-time updates across millions of photos across Flickr friends, Flickr Commons, and by tags and geo-location using the Flickr Real-Time API.
The most popular API, in terms of mashup count, is far and away the Google Maps API, which accounts for 41% of all mashups. But when it comes to the most popular pair of APIs, Flickr and YouTube mashups are the most common. Not to be outdone, Google Maps joins Flickr in a near second place.
Cloud APIs are all about the endpoints: some services follow the current trend of providing a RESTful end point, others use older protocols such as RPC or SOAP, some use newer - push focused - endpoints like WebSockets or HTTP Streaming, others may offer a number of different endpoints to meet different requirements and some just use what seems to be best for a specific job which might mean not strictly following protocol rules. But is providing an endpoint to a service alone good enough? Should a developer really have to care about how a service is built or accessed when they can use a client library?
There is nothing more satisfying than sharing that once in a lifetime shot with the world, except maybe seeing that it has been viewed by a few thousand people. These kinds of stats have been collected by Flickr for quite some time, and now they are available to developers thanks to some new functions added to the Flickr API.