If you haven’t read part 1 and part 2 this API series, check the a links on the right 🙂
A successful API is more than a feature; when you view your API as a product, it can be an enabler of your business strategy. Part of the magic of APIs is that creative developers find uses that the API designers never envisioned. If APIs are well designed and easy to use, this can be an enormous benefit and opportunity, turning your service into a platform that can grow in many ways.
If you haven’t read Part 1 of this series, click here.
Organizations often decide to build an API without fully considering key success factors or without first engaging their stakeholders. I saw this first hand at a previous employer and it is very painful, not just for the company, but for the consumers of the API, which can have long-lasting repercussions.
To continue on from my last post on API’s and their Business Value I did a few years ago. I thought I would write an updated post on API’s (Application Programmer Interfaces) do a little deep dive. APIs have had a big impact on my last role and bigger impact on my current role as a PM @ 5nine Software, and thought I would share my knowledge and research so far. APIs are not scary 🙂