Applying a Developer-Centric Approach to API Design from API Architect Ronnie Mitra

Please download to get full document.

View again

All materials on our website are shared by users. If you have any questions about copyright issues, please report us to resolve them. We are always happy to assist you.


  Designing an API from scratch can be a daunting task, but focusing on developer experience (DX) can act as a guiding light for API designers. In this session, we will explore the topic of interaction design and how it is changing the way we design web APIs today.
Related documents
  • 1. The “I” is for Interaction!Applying a Developer-Centric Approach to API DesignRonnie MitraPrincipal API Architect - EuropeLayer 7 API Academy
  • 2. API Managementon-premise virtual cloud
  • 3. API AcademyMike Amundsen Ronnie Mitra
  • 4. The “I” is for Interaction!
  • 5. Ok. It isn’t really.
  • 6. Interaction Design
  • 7. UsabilityHuman-Computer-Interaction User Experience Design Goal Oriented Design
  • 8. A user-centric view of design.
  • 9.
  • 10. Well designed products are easier to use.
  • 11. Good design matters for Web APIs too.
  • 12. We want:“Frictionless” integrationHigh rates of adoptionLow cost integration
  • 13. Focus on the developer experience (dx)
  • 14. Portal API
  • 15. Why is this difficult?
  • 16. Reason #1We project our own perspective.
  • 17. Your code is not your API.Your data model is not your API.
  • 18. Reason #2We project our own biases.
  • 19. Never use SOAP? Why?
  • 20. Consider keyboards…
  • 21.
  • 22.
  • 23.
  • 24. It doesn’t matter that you don’t like SOAP.
  • 25. What matters is what your developer base thinks!
  • 26. Reason #3We make bad assumptions.
  • 27. API publishers are also developers.
  • 28. Reason #4We lack the time and money required for design
  • 29. “Best practices”, patterns and standards become shortcuts
  • 30. Am I RESTfull enough?
  • 31. So, how can we do better?
  • 32. Developer-centric design requires effort and diligence.
  • 33. Design with the developer in mind.
  • 34. Ask them.
  • 35. • Interviews• Surveys• Listen (blogs, presentations, tweets)
  • 36. "If I had asked people what theywanted, they would have saidfaster horses.“ – Henry Ford?
  • 37. • Observe• Prototype• Historical Data
  • 38. Consider all aspects of the DX: Registration Security Troubleshooting Learning Interface Style
  • 39. RegistrationLazy RegistrationSocial IntegrationPersonalization
  • 40. Development Activity Cycle1. Learn2. Code3. Implement4. Test5. Fix
  • 41. Learn PortalCode API Test
  • 42. Learn APITest
  • 43. API explorers and “livedocumentation” can shorten the gap between visibility and feedback.
  • 44. InterfacesI use GET to write to your API?
  • 45. InterfacesHypermedia can provide: Affordances Constraints Feedback API
  • 46. SecurityNeeds to be considered from a developer point of viewOAuth 2 is easier to implement than OAuth 1 (for your developers)
  • 47. How?1. Identify a Target Audience2. Learn about the audience3. Make API design choices that are developer-centric4. Prototype and get feedback5. Iterate
  • 48. Focus on the interactions that take place, rather than the interfaces we expose
  • 49. Great API design can thrive in a developer-centric environment
  • 50. The “I” is for Interaction!Applying a Developer-Centric Approach to API DesignRonnie MitraPrincipal API Architect - EuropeLayer 7 API Academy
  • 51.
  • Related Search
    We Need Your Support
    Thank you for visiting our website and your interest in our free products and services. We are nonprofit website to share and download documents. To the running of this website, we need your help to support us.

    Thanks to everyone for your continued support.

    No, Thanks