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
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
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
87. Succeed with a Developer-centric API Strategy
Ronnie Mitra
Principal API Architect â Europe
Hinweis der Redaktion
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