Instagram may be looking to find its location data from Facebook, dislocating Foursquare. Pitney Bowes and IBM to cooperate using PB’s location services APIs with IBM’s cloud platform. Plus: Google’s cloud platform adds new features and price cuts, security breach created as users publish Amazon Web services keys on Github, and 8 new APIs.
Japanese start-up Linkify has bypassed an API release and gone straight to an SDK launch of their latest mobile developer tools. Linkify aims to provide monetization opportunities by using keyword and graphics analysis to add paid links directly into content on mobile Web sites and app pages. Cofounder and CTO Ikuya Yamada spoke with ProgrammableWeb about how developers can commercialize their content and Linkify’s roadmap to an augmented-reality future based on text and graphics analytics.
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.
Having an intuitive developer portal is only the beginning of building your API community. Both online and offline aspects can really help you engage with the developers who use your API. The same methods can also help you identify or attract potential developers. These are all pretty much must-haves, but be sure to share in the comments the ones that you think are most important.
There are a number of ways to discuss API popularity. One of the common methods ProgrammableWeb has used is by mashups, the number of completed apps. However, there may be a leading indicator before developers have even started writing code. The “track” functionality on ProgrammableWeb lets developers declare an interest in receiving updates on particular APIs. By diving into this data we can see many things. For example, recently developers have loved travel. Overall, social and visual APIs rule
In earlier pieces about APIs where developers pay for access, I’ve covered methods of pricing APIs and even shared the top three API trial methods. However, some of you are probably not that far along in that process. You may have a good idea for a developer-focused company. Or perhaps your company solved a big issue internally and you want to expose your solution as a new revenue stream. In any case, before you dive into your pricing page and start selling your API, you’ll want to consider some basic questions about the problem, your solution and whether you’re able to support your potential customers. These are the three questions to ask yourself if you sell an API.
Google has opened its Glass Mirror API. Di-Ware announces App competition, initial deadline December 20. Plus: Salesforce CEO Benioff promises full review of hackathon after cries of unfair judging, API vendor and consumer positions on robots.json are explored, and 11 new APIs.
Appy Pie, cloud based mobile apps builder, continues to add to its list of supported APIs. Its latest additions include some of the most prevalent names in image sharing: Facebook, Flickr, Pinterest, Picassa and Instagram. The image newcomers to the Appy Pie portfolio allow developers to share images in realtime with users.
Photo APIs have long been a staple of developer applications. There are more than 350 photo APIs in the ProgrammableWeb directory and almost 800 photo mashups. However, most applications integrate with photo sharing services, like the Flickr API and Instagram API, missing the real power of photo APIs. This post identifies four ways that APIs are getting smart by using image recognition technology to find faces, words and more.