On Tuesday, social media giant Twitter announced that it is buying Data as a Service (DaaS) provider Gnip for an undisclosed amount. Gnip, which is one of several companies that sell access to the firehose of the content posted on Twitter, was founded in 2008 and today offers data from a number of popular user-generated services in addition to Twitter.
HTC announced the One smartphone this week, its new flagship device for the year. The One is a sequel to last year’s well-liked smartphone and ratchets up the sex appeal with an all-aluminum design. Its feature set, which includes a luscious 5-inch HD display, zippy four-core Qualcomm Snapdragon processor, and shiny metallic colors, will let it compete well against similar phones from other manufacturers. HTC believes developers can plan a role in the One’s success, too, with new APIs for the camera and BlinkFeed.
There are major advantages to today’s applications being built atop APIs. If you’re reading ProgrammableWeb, there’s a good chance you know all about integrating with other services. The major disadvantage of modern distributed architecture is pretty obvious—someone else’s service could go down and it’s outside of your control. You might not even know a service is down, which is why many top API providers are now making status pages available. These sites help communicate to developers when anything is amiss with the API.
Augmented reality applications are in demand as businesses try to create an application experience that is truly memorable. The Autonomy unit of Hewlett-Packard created Aurasma to enable building those types of application. The Aurasma content management system exposes triggers through which videos, images or 3D models are automatically launched.
Facebook’s $19 billion acquisition of cross-platform messaging service WhatsApp was obviously a boon for WhatsApp’s founders, employees and investors, but it also proved to be a good thing for several of WhatsApp’s biggest competitors.
Twitter will turn eight in March and the Twitter API will have its birthday toward the end of the year. It’s been a long ride for something that started as sort of a side project. The service, and especially its API, saw quick growth, as the platform expanded, added features and eventually had to grow up.
In a previous post I covered six great ways to engage your API community. It was based on seeing thousands of APIs—some that received developer attention and some that fell flat. Now I have dug into ProgrammableWeb’s directory to find the features that really seem to make a difference. Comparing the top 100 APIs to the rest of the pack, it’s clear that community support is a huge differentiator.
Twitter for Websites enables you to integrate individual tweets and timelines right in your website or application. These tweets and timelines can display media, including photos, videos and article summaries. They are also fully interactive, allowing your readers to interact with them just as they would on Twitter.com.
As the number of APIs grows, more people are becoming familiar with the term. I had a taxi driver who knew about APIs, although that was in tech-heavy San Francisco. Despite becoming more known, “API” is not a term most mainstream users will use. Yet many of these same people are already asking for APIs—they’re just not using the term. Here are three ways mainstream users are asking for APIs.
In a rare API conference event appearance, Twitter graced the stage at last week’s APIDays Paris. The social giant shared some insight into current API usage among third-party developers and gave some read-between-the-lines signs of how it intends to work with API partners in future.