ProgrammableWeb’s Editor-in-chief David Berlind moderated a lively panel session at the recent DeveloperWeek conference in San Francisco. The panel included industry thought leaders Jason Harmon from PayPal, Jeremiah Lee Cohick (Fitbit), Alex Salazar (Stormpath), Uri Sarid from MuleSoft (the parent company of ProgrammableWeb) and John Musser, founder of both ProgrammableWeb and API Science. In an hour-long panel on “emergent APIs,” panelists covered API design, SDKs versus APIs and the challenge of API versioning. Bonus points: Each shared their number one piece advice for developers in businesses charged with creating their first API.
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.”
Businesses exploring an API strategy are asking themselves: private, partner or public? Since the start of the year, there has been a lot more thinking aloud about how businesses decide whether to start with an internal (private) API; use partner APIs to manage specific business relationships; or jump straight into designing external, developer-facing open (public) APIs.
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.