For people who make APIs, it is easy to focus on your API as your “product”, but in reality an end user’s experience is in fact defined by whatever they can pull down from their favorite language’s package manager. As a developer, writing your own library to use someone’s API is rarely desirable, especially if there is another API that you could use with the same functionality and a library in your language. But how is an API provider supposed to build these SDKs in a scalable way so that they aren’t crushed by the maintenance burden of future API developments? This talk will cover a few of the common strategies:
High impact blog posts and eBooks on API business models, and tech advice
Connect with market leading platform creators at our events
Join a helpful community of API practitioners
Can't make it to the event? Signup to the Nordic APIs newsletter for quality content. High
impact blog posts on API business models and tech advice.
Become a part of the world’s largest community of API practitioners and enthusiasts. Share your insights on the blog, speak at an event or exhibit at our conferences and create new business relationships with decision makers and top influencers responsible for API solutions.