Developers love APIs for many different reasons. They might browse the ProgrammableWeb directory to be inspired and get ideas for a project. They might be delighted to tie together two disparate sources with their code. One of the biggest reasons developers should love APIs is that APIs save them time — time they can spend elsewhere. And yet, even the smartest developer can be caught answering the question “Can we build it?” with an enthusiastic “Yes we can.”
Email is one of the oldest mediums of communication on the Internet, and, for many companies, it’s still one of the most important. Delivering email and tracking email campaigns reliably is crucial to success for countless businesses today.
DeveloperWeek has started in San Francisco, promising to offer a wide range of activities during the week, including two days of packed conference sessions, coding workshops, tech start-up open days, and evening hiring mixers. To kick start the week of events, DeveloperWeek hosted a hackathon at the Rackspace offices in San Francisco’s SoMa district.
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.
Oscar-nominated film Her would have us believe that in the future we may fall in love with our operating systems. Or at the very least, it shows a much more fluid interaction with technology. Through mostly a speech interface, people are able to read email, search and view photos. Merge this with the Internet of Things that is taking over our present and you can see the power of APIs that speak your language.
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
E-HAWK, cyber intelligence provider focused on combating fraudulent sign ups, has released the Vetting API Connector. The API automates the various vetting tools E-HAWK has deployed to analyze sign ups to determine the risk of fraud. The technology analyzes risk by vetting IP address, email, phone number, location, device and more. Based on risk levels, companies utilizing E-HAWK tools can set automatic responses to fraudulent activity.
For many APIs, a developer portal is the first interaction a developer will have with the API. Typically, this is where a developer finds documentation, code examples, an app gallery and other details that connect them with the API provider. If you want developers to use your service, you’ll aim to make everything within the developer portal as clear as possible. Consider these six steps to bring clarity to your current and future developers.