just as much consuming as you are building. Your developers should be using the APIs as much as they’re developing them. It’s important for your dev team to see what an external developer’s experience will be when using your API. Knowing what that experience is will help your support and outreach efforts as you work to inspire and equip your external developers through faith-building and education.
3. Develop for Everyone: Adam Fuchs of AWS (Amazon Web Services) made note that he doesn’t make any distinction between internal and external developers, as you need to build your APIs for both audiences. No group should get preferential treatment, and you should use what your customers will use. This helps inspire quality in the APIs you build. Your guatemala phone number list API is your contract with the customer. It’s imperative to listen to customer requests and feedback and allow that to drive development. Treat your developer community as a democracy, and get your internal developers in front of the external ones to create a powerful relationship that can pay huge dividends as your program grows.
4. Allow for Easy Access: Self-service API keys are essential. You must have a low barrier entry to your API. Once developers have access, use forums or applications such as Basecamp to guide conversations. Partner with your external developers through their development process. Look to your developers for guidance: track GitHub activity, Stack Overflow, blogs, and forums for feedback and issues. A free tier to access your API is also crucial. Let developers learn and test your API without having to absorb a cost.
6. Engage the Community: Have a hands-on approach to your platform and interacting with the dev community. Attend meetups and hackathons, and send your developers to them as well. Make sure your documentation and support channels are well-indexed in search engines and keep the dev community engaged. API walkthroughs, reference guides, and white papers are all ways to do this. Twitter is also a great way to reach the community.
7. Know Your KPIs: Make sure you’re measuring your successes in the right ways. Develop the KPIs around your program, and reevaluate them constantly. For example, it’s not enough to just measure call volumes, but you must tie those volumes to billing metrics and overhead. What did it cost to execute on that volume? What portion of the calls to your API are actually making an impact on revenue?