Evangelism and advocacy
In this tutorial, we will learn and understand about Evangelism and advocacy.
The API developer
If the architect creates the plans and drafts for the construction of the API, the API developer is the actual builder. However, their goal is to produce intuitive and highly consumable APIs. They fulfill this goal not only by building the API itself but also by contributing to resources. This will help developers most effectively leverage the API, such as documentation.
However, the API developer should be an expert web developer, well-versed in both consumption- and exposure-oriented API development. They should have a strong understanding of the
- Firstly, ins and outs of the API management platform to implement security policies
- Secondly, traffic management.
- Lastly, about other protocols that support the scaling of APIs per standards consistent across the organization.
The API evangelist
- Like any product evangelist, the API evangelist is the voice of API consumers. That is to say, the evangelist should deeply understand developers and ensure they have all the things. However, this role is responsible for the vital task of managing the developer portal and ensuring developers have access to detailed information on the product offering. This also include documentation and software development kits (SDKs).
- Further, they are responsible for internal and external developer outreach. This outreach might include not only answering questions, running hackathons, and bringing developer feedback to the API team to inform product roadmap discussions. But, also marketing the APIs via SEO, targeted ads, and other methods.
- Lastly, evangelists can play a crucial role in attracting partners to the company’s APIs. And, thus in expanding the ecosystem of participants leveraging the company’s offering.
The API champion
The API champion is to the executive boardroom or the lines of business what the API evangelist is to developers. They connect an organization’s API programs to the business value they provide by translating data points that make sense to technical leaders into metrics.
However, they should be analytical thinkers and powerful influencers that can develop strategic business goals while paying attention to the technical capabilities of an API product offering. And, they should always understand how the business benefits of API products apply to app developers and customers as well. Further, they should ensure the team continues to move in an agile fashion. This is so that the organization can get more MVPs to market and open the door to new lines of business.
Reference: Google Documentation