The Internet of Things started 2014 with a bang, stealing the spotlight at the 2014 International CES, where a number of shiny new cloud-connected devices and appliances were showcased, like the Kolibree connected-toothbrush and the new Audi A3, with its Audi Connect telematics system.
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.
APIs and data delivery go hand in hand, with APIs being the core mechanism for transferring information between dissimilar systems. Web applications have relied on APIs for a variety of tasks and chores, making coding for API integration a core competency and critical element for those building Web applications.
Here is an interview with Scoreoid founder and CEO, Almog Koren. Scoreoid allows you to gamify apps using the Scoreoid API and backend as a service. With 3000+ games and almost 1.8 billion monthly sessions- this is one API startup that seems to be going places.
This is the second of two articles on the growing trend of API-first design. In this article Uri Sarid, CTO of MuleSoft (parent to ProgramamableWeb), discusses the approaches to API-first design. He touches on the value of this approach and how it allows businesses to optimize for a great API instead of having the API simply be a reflection of existing code. Previously, Patricio Robles explored real-world examples that illustrate why API-first design is an emerging trend.
WS-REST.org has announced that it will host the fifth edition of the International Workshop on Web APIs and RESTful Design at the 23rd International World Wide Web Conference this April in Seoul, South Korea. The first workshop was held in 2010. As APIs have continued to drive innovation in the connected world, the workshop has continued to refine its scope of study, broaden its expectations and increase interest. As the organizers begin to develop this years agenda, PW caught up with Carlos Pedrinaci, a research fellow at The Open University, UK, and one of the event organizers.
Given the rabid nature of most of their fan base, professional football teams were among the first organizations to see the value of developing mobile applications to get closer to those fans. The problem for most teams now is the stadium WiFi experience they provide to their most loyal fans leaves much to be desired.
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.
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.