Succeed with a Developer-Centric API Strategy - Ronnie Mitra, Principal API Architect, Layer 7 @ Apps World
•Download as PPTX, PDF•
3 likes•1,445 views
DX as the key to building a great API Going beyond usability and simplicity in design Considerations for the API lifecycle Treating your API like a product
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (6)
Similar to Succeed with a Developer-Centric API Strategy - Ronnie Mitra, Principal API Architect, Layer 7 @ Apps World
Similar to Succeed with a Developer-Centric API Strategy - Ronnie Mitra, Principal API Architect, Layer 7 @ Apps World (20)
More from CA API Management
More from CA API Management (20)
Recently uploaded
Recently uploaded (20)
Succeed with a Developer-Centric API Strategy - Ronnie Mitra, Principal API Architect, Layer 7 @ Apps World
- 1. Succeed with a Developer-centric API Strategy Ronnie Mitra Principal API Architect – Europe
- 3. Strategy Identify goal(s) Define activities that support the goal
- 4. Your API is not your strategy
- 5. Your API enables your strategy
- 6. Revenue Source Consumer Reach Marketing Innovation Integration Light Bulb designed by Jean-Philippe Cabaroc from The Noun Project
- 7. API Strategy Identify goal Define activities that support the goal
- 9. Lots of Dials Developer Outreach Interface Design Marketing Support Visibility Control Registration Change Management
- 10. Good strategy involves making decisions
- 12. A developer-centric approach will help you make decisions.
- 13. Product Design
- 15. Usability Human-Computer-Interaction User Experience Design Goal Oriented Design
- 17. A user-centric view improves product design.
- 18. A developer-centric view improves API design.
- 19. three forms of design
- 22. What does the API do? Where is it located?
- 23. The stereotypical SOA approach Functionality focused Everything is a service Service catalog Make people use it
- 25. How do I use the API? How easy is it for me to accomplish my own goals? How much of my time do I need to commit?
- 26. The API Revolution Developer focused Deployed in competitive markets
- 27. Don’t forget: Usefulness > Usability
- 29. How does using the API make me feel?
- 30. Developer Experience (DX): 1. the sum of interactions between the developer and an API owner
- 31. Developer Experience (DX): 1. the sum of interactions between the developer and an API owner 2. the emotive impact of API usage on the developer
- 32. sometimes experience can trump usability
- 34. I want to add weather forecast data to my mobile app. An API should help! http://www.southparkstudios.co.uk/avatar
- 35. I’m having trouble finding an API that does what I want. http://www.southparkstudios.co.uk/avatar
- 36. the registration process is a nightmare! http://www.southparkstudios.co.uk/avatar
- 37. What is XML-RPC? I don’t even have an XML parser! http://www.southparkstudios.co.uk/avatar
- 38. Why is everything in Fahrenheit!? http://www.southparkstudios.co.uk/avatar
- 39. small annoyances add up to create a poor experience
- 40. API Interactions
- 41. Dev Portal API
- 42. Dev Portal API
- 43. is a developer-centric strategy obvious?
- 44. why is it difficult to design usable APIs?
- 45. We project our own perspective. We project our own biases. We make bad assumptions We lack the time, money or incentive.
- 46. Reason #1 We project our own perspective.
- 49. Reason #2 We project our own biases.
- 55. OR
- 56. It doesn’t matter that you don’t like SOAP.
- 57. What matters is what your developer base thinks! (and what the business objective is)
- 58. Reason #3 We make bad assumptions.
- 59. API publishers are also developers.
- 60. “I built a mobile app once.” may not qualify you to understand your mobile developers
- 61. Reason #4 We lack the time, money or incentive for good design
- 62. “Best practices”, patterns and references become shortcuts
- 63. We project our own perspective. We project our own biases. We make bad assumptions We lack the time, money or incentive.
- 64. overcoming the usability challenge
- 65. developer-centric design requires effort and diligence.
- 66. Mental Models
- 67. Mental Models
- 68. Design with the developer in mind.
- 69. who are our users?
- 70. Josh I blog, I tweet, I code and I swear. Age: 25 Occupation: Web/Mobile Developer Technical Profile: 7 years experience, hackathon
- 71. why are we always building APIs for Josh?
- 72. Tony I’m never leaving this company. Age: 45 Occupation: Enterprise Developer Technical Profile: 27 years industry experience, skilled in Java, VB, COBOL.
- 73. You can’t design for usability if you don’t know who is using your API
- 75. try using your API from a developer perspective
- 76. + =
- 78. good API design is user-centric
- 79. is good security user-centric?
- 80. practical API design becomes a series of tradeoffs
- 81. What keeps API owners up at night… Brand Control Data Security Threat Prevention Resource Protection Availability
- 82. the API strategy challenge – balancing control and usability reduce usability impact (for our user) focus on experience (sum of interactions) use just as much security as we need
- 86. Establish Business Goals Establish API Goals Identify Target Users Design for your users
- 87. Succeed with a Developer-centric API Strategy Ronnie Mitra Principal API Architect – Europe
Editor's Notes
- It’s tough when you are faced with that blank sheet of paper
- Lots of methodologies and terminology
- Coined in the 1980sBut rooted in the design ideas of industrial age products and how users interact with technology
- Lots of methodologies and terminology
- We are not simply producing products that perform a funciton, but we consider how people (or users) will interact with the product.
- We are not simply producing products that perform a funciton, but we consider how people (or users) will interact with the product.
- On our own we could create an API in 20 minutesPut us together and it would be much more difficult
- What is this thing that we are exposing? What is the data or service that we are making available? What features or functions are we providing?
- What is this thing that we are exposing? What is the data or service that we are making available? What features or functions are we providing?
- What is this thing that we are exposing? What is the data or service that we are making available? What features or functions are we providing?
- What is this thing that we are exposing? What is the data or service that we are making available? What features or functions are we providing?
- What is this thing that we are exposing? What is the data or service that we are making available? What features or functions are we providing?
- Think: greater than the sum of its parts
- But we need to expand the focus to include our user, the developer
- APIs are all about connectivity.
- APIs are all about connectivity.
- APIs are all about connectivity.
- APIs are all about connectivity.
- APIs are all about connectivity.
- Different social conventions.Another form of this, is the question of RESTfulness.
- APIs are all about connectivity.
- APIs are all about connectivity.
- [there was something else I realized after this pres. for Reason #4. – try to remember]Talk about when API dsigners don’t botyher with usability – selling to enterprises. (or do I leave this till later?)
- APIs are all about connectivity.
- APIs are all about connectivity.
- Designer mental model vs. user mental model
- Designer mental model vs. user mental model
- APIs are all about connectivity.
- Make bold choices
- Make bold choicesGoals should correlate to bigger strategy