API Developer Success: Looking Beyond Developer Experience (DX)
Everybody is talking about Developer Experience (DX) for APIs, but is that all that matters? What about a more holistic perspective that gets you past "Time to first Hello World" metrics? Let's talk about Developer Success!
Pronovix CEO Kristof Van Tomme has something in mind that he calls "developer success", and it's something that changes your attitude towards designing and managing APIs and helps you to get more out of your #API landscape. What are two simple way to improve developer success?
👉 Each API should have a business model: Make sure that for each API that you have it is documented how this is going to benefit your organization. This helps you to explain why this API is worth keeping around, and also helps you reflecting on what each API's business value really is.
👉 Internally and externally facing APIs should be approached differently: Public and partner APIs need to be managed as individual products whereas private APIs are better treated as part of your API platform. Treating these classes of APIs in the same way is likely to cause problems.
Here are additional resources around the topic of developer success:
🎥 Designing Private, Partner, and Public APIs: What's the Difference? - • Designing Private, Partner, and Public API...
🎥 Is API Developer Experience (DX) Overrated? What's more important than DX? - • Is API Developer Experience (DX) Overrated...
👉 Pronovix Blog: Developer success: looking beyond developer experience - https://pronovix.com/blog/developer-s...
👉 Jabe Bloom: The Three Economies an Introduction - https://blog.jabebloom.com/2020/03/04...
If you're interested in regular news from the #API space, subscribe to "Getting APIs to Work" here: / erikwilde
#api #apilandscape #apidesign #apistrategy #designthinking #apieconomy #apimonetization #gettingapistowork #businessstrategy #digitaltransformation #apimanagement #apiplatform #apiproduct #apifirst