Why you need a Developer Relations team for your API
•Download as PPTX, PDF•
0 likes•214 views
Providing a good API product to your users is the minimum. With all the competition developers have many more expectations than quality APIs; developer community, documentation, tutorials, developer tools and this is exactly where the Developer Relations (DevRel) team fits. In this talk we’ll discuss why your API product needs a DevRel team and how it can drastically upgrade the face of your API program and satisfy your users. We’ll talk about how the DevRel team can engage your users to nurture a long-term community and make your API product successful.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Why you need a Developer Relations team for your API
Similar to Why you need a Developer Relations team for your API (20)
More from Pronovix
More from Pronovix (20)
Recently uploaded
Recently uploaded (20)
Why you need a Developer Relations team for your API
- 1. Why you need a Developer Relations team for your API Anna Tsolakou API The Docs Virtual 2021
- 2. Anna Tsolakou Developer Advocate at Amadeus for Developers AnnaTsolakou tsolakoua 2
- 3. Market Today 3 Many quality APIs per industry Great technology & services Many more expectations Developer tools, tutorials, community How to succeed? This is where the DevRel team fits
- 4. What is a Developer Relations Team 4 You’ve heard about _Developer Evangelist _Developer Advocate _Technical Writer and more…. A lot of debate Who really belongs to DevRel? Truth is it’s all DevRel Diverse team with different skills & backgrounds
- 5. The DevRel team is all about 5 Understanding developers How they feel about your product? ---- What they build and how to succeed Filling the gap API <> developers Raises customer voice internally ---- The public face of your API Wearing different hats Involved in many different tasks ---- Adapt quickly to changes
- 6. Why DevRel team 6 Developer experience Awareness, adoption & engagement Developer community Integrate easily & efficiently the APIs Build an attractive product roadmap Feedback process 1 2 3
- 7. 1. Developer Experience SDKs Documentation & Guides Demo apps Customer support
- 8. SDKs 8 Developers expect _Reduced technical complexity _API access in their own environment _Simple authorization _Error handling _Code examples What are software development kits (SDKs) Developer libraries containing the tools and documentation to build applications for a specific programming environment.
- 9. SDKs Experiment with a senior developer 9
- 10. Documentation & Guides 10 API docs _Complete _Consistent & clear _Room for improvement #Your customers Wide variety of experience and industry knowledge Guides _Functional & tech guides _Video tutorials _Educational content
- 11. Since DevRel started growing 11
- 12. Demo apps 12 WHY _Inspire & give ideas _Reduce onboarding _Promote APIs HOW _Think of a use case _Include new APIs _Publish the code FOR WHO _Early stage startups _Potential customers _Hackathons & students
- 13. Demo apps built 13 How safe is the hotel’s location and what attractions & tours can I see? Do I get a good deal?
- 14. Technical & functional DevRel expertise in APIs and industry Feedback source Collecting market trends Customer ideas & struggles Multiple channels Not only support email, but GitHub, Twitter, Stack Overflow + 14 Customer Support API health monitoring Identify bugs before users
- 15. 2. Developer Community Engagement Metrics 2019-2020 Online developer community
- 16. Hackathons Awareness Innovation Feedback Conferences & meetups Knowledge sharing Networking Feedback Online developer community Single place for users Support Networking Embrace Open-source Demos & SDKs Developers love using and contributing to OS Trust building 16 Engage with the community Online Online Online Offline Offline
- 17. The last two years 17 Conferences & Events Talks delivered Hackathons Audience reached 2019 21 17 6 6k 2020 16 14 4 28k
- 18. Online Developer Community 18 Activities _Support hours _Networking hours _News sharing _Announcements Since the 1st week _Many interactions _1 SDK contribution _1 OS project _1 blog article
- 19. 3. Feedback Collect Feedback Share Feedback Feedback examples
- 20. Customer support channels Emails, Twitter, GitHub, Stackoverflow, Linkedin Events Hackathons, Conferences, Local meetups Survey Scheduled calls For specific feedback Online developer community 20 Collect Feedback
- 21. Share Feedback 21 _Invest in a tool to consolidate feedback _Add feedback & user _Share with internal teams _Prioritise feedback _Get back to user when a feedback is implemented
- 23. We talked about SDKs Docs & guides Demo apps Customer support Hackathons & events Online dev community Collect & share 23 Developer Experience Feedback Developer Community
- 24. Happy community Developers who love your product and talk about it Reduce onboarding Successful customers Their success is your success Big player in the market 24 Payoff based on our experience
- 25. Does anyone have any questions? https://twitter.com/AnnaTsolakou developers.amadeus.com 25 Thank you
Editor's Notes
- My name is Anna Tsolakou. Today we are going to see Why you need a DevRel for your API Amadeus is the leader technical provider in travel industry and Amadeus for Developers is the Open API program that provides travel data and services
- This is our story and I am sure you have heard many similar stories from API users. And if we think about the market day there are so many API providers with great technology and services. But quality API is the minimum. Developers have many more expectations: Tutorials, developer tools, a developer community around the product to share information and find interesting content. And this is exactly where the developer relations team fits. The developer Relations team make all these expectations reality and make you a big player in the market.
- At Amadeus for Developers since the beginning we identified three reasons why we need a DevRel team. 1, 2, 3. And I’d like to show you how the DevRel team is involved and best practices.
- Providing a well-designed, easy to use API product is a great start, but have you ever measured the amount of time and code needed to actually make a first call? We did – it took an experienced developer 10 minutes and 55 lines of code. Providing SDKs to help developers get started quickly can reduce the time to the first hello world to just three minutes and ten lines of code. Including authorization, access to all APIs, code quality, error handling and more can really solve the hands of your users.