Box is on its way to joining the API Billionare club. Streak CRM builds on Google Cloud Platform APIs. Plus: WallaBee becomes the first iOS game to support Passbook, Trigger.io and Apigee enable fast mobile app development for the enterprise, Text My Bus eliminates wait time for Detroit citizens and 11 New APIs.
The debate over RSS never seems to end. 2011 kicked off with a widely read post predicting the decreasing influence of RSS in 2010. There have been responses from Fred Wilson and GigaOM that argue it is still relevant today. We believe that it continues to be a solid mechanism for web sites to aggregate data from multiple sources, as displayed by the 121 RSS APIs in our directory. In this post, we’ll look at RSS beyond blog syndication.
We kicked off 2011 with our report on API growth. We list more than 2600+ APIs in our directory, with social and mobile APIs seeing major growth. APIs will continue to increase and 2011 should see the a move from simply providing an API to providing great APIs. The beginning of the year typically gives rise to several articles that tell us about what to expect in the year ahead and APIs are no different, with those below from GigaOm.
There are a number of ways of delivering data in real-time but until recently it has looked like PubSubHubbub, with the backing of Google, was going to be the preferred method. However, the past couple of weeks have seen a couple of interesting developments which could indicate that the developer community may actually prefer HTTP Streaming.
Popular location-based social network Foursquare quietly made the long-teased new version of its API publicly available Tuesday. The changes, embraced by its developer community, include JSON-formatted responses and OAuth-only authentication. Even though the new API is characterized as in beta, the company has also deprecated the previous version, announcing it will no longer be available by the middle of next year.
API providers and developers are making their choice quite clear when it comes to choosing between XML and JSON. A nearly unanimous choice seems to be JSON. Several API providers, including Twitter, have either stopped supporting the XML format or are even introducing newer versions of their API with only JSON support. In our ProgrammableWeb API directory, JSON seems to be the winner.