Articles

When you create rules, procedures in an organization, that doesn't mean that people will actually follow those. People will use those rules and procedures as their environment inside of which they act. Whatever rule you set up, don't ever expect people to follow: you always have to look for the unintended consequences. The goal of this article is to make you curious about: 1. Systems thinking 2. Complex Adaptive Systems 3. The role of APIs in Digital Transformation 4. The role of devportals in Digital Transformation

In this talk Kristof explains the differences between public and private APIs, introduce upstream developer experience, and explain how it can improve downstream DX. Introduce experience design (a.k.a. gamification) and Innersourcing (open sourcing practices behind the firewall) and describe how they could be used on internal developer portals.

What Is a Developer Portal? A trust signal for your API. A self-service hub. A dashboard for your API products. A list of endpoints is not enough. We provide you with an infographic to help explain.

Developer portals play not only a technical role, they also play a somewhat obscure commercial role. We don't like to say that this is a commercial site, but actually it is also about promotion. You have to explain what you do – preferably not in a hard-core manipulative way. For that, you need more than reference docs. How to get started? What does that API do? A lot more than just the very technical aspects need to be explained. A less well circulated purpose of developer portals is their being a trust signal. They engender trust by showing how much investment went into building that portal. They have to show that the API services documented on that portal will keep on existing and will get reliable support long term.

API friction can be seen as the inverse of developer experience, and it is a great conceptual device to help you identify issues in your API products. To create a great developer experience (DX), it is important to remove as much friction as possible from the developer’s journey.

In this guest post Jenny Wanger, Product Manager at Arity, gives an overview of the most important developer experience KPIs (key performance indicators).