Posts Tagged: dx

API-playground-sandboxes-virtualization

Virtualization, Sandboxes, and Playgrounds for a Wholesome API

An API is only as good as it is known. Getting an API into a developer’s hands, demonstrating the power of your solution, and providing an environment in which they can test and manipulate data in a controlled, monitored way is perhaps one of the most important unsung heroes of API publication. Read more

how-to-market-an-api

eBook Released: How to Market an API

We’re happy to announce a new eBook release! We’ve assembled our best advice on API marketing, developer relations, and platform advocacy into a single volume. Grab a copy of How to Successfully Market an API for free HERE, or name your price on LeanPub. Read more

accumulating-feedback-4-questions-to-ask-API-consumers

Accumulating Feedback: 4 Questions API Providers Need to Ask Their Users

American activist Bryant H. McGill once said, “one of the most sincere forms of respect is actually listening to what another has to say.” For API providers, listening to the average user, accepting feedback, ingesting these experiences, and iterating on this information is a powerful exercise. Read more

Finnish-Startups-Advise-API-Practitioners-on-the-API-Stack--Pre-Helsinki-Event-Feature

Finnish Startups Advise API Practitioners on the API Stack: Pre-Helsinki Event Feature

How many organizations are adopting an API strategy in Helsinki? Quite a few — for one, Helsinki arguably is the most successful city in the world using open data, with an active developer portal (Dev.Hel.fi) enabling the creation of new applications on top of city data to promote participatory democracy. Read more

API-model-canvas-developer-experience

API Model Canvas: Developer Experience is a Key Ingredient of Quality APIs

According to The State of API Survey Report 2016 by Smartbear, nearly 85% of the respondents agree that API quality is crucial to their organization. The same survey identifies the top three reasons keeping organizations from delivering quality APIs are:

1) Increased demands for speed 2) Lack of integration between tools and systems 3) Managing expectations of different stakeholders

A remedy for the first reason can be found by fine-tuning architecture and optimizing code. Read more