Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
API Design in the Age of
Bots, IoT, and Voice
James Higginbotham
@launchany
https://apideveloperweekly.com
The Road So Far…
1990s
Distributed
Object Integration
2000s
Corp-to-Corp
Integration
2010s
+
Mobile/Data
Integration
The State of API Design in 2017
APIs are stuck in the land of CRUD
API Conversations with CRUD
API Design is an architectural
concern that combines
business, product design, and
technology
Messaging Platforms
When APIs Meet Jobs-To-Be-Done
1. Hypermedia
and HATEOAS (again)
Choose Your Own Adventure for APIs
When APIs Meet Jobs-To-Be-Done
{
…
"_links": {
“self": {"href": "/approval-requests/d796f2d0eb72492bb088"},
“approve": {"h...
2. Event Subscriptions
https://www.asyncapi.com/
1_Blank
IoT
Common Alexa Commands
3. User-First, Capability-Driven API Design
Visual Voice
GET https://api.myexample.com/projects
Accept: application/json;q=0.5,text/html;q=1.0
4. Content Negotiation For Visualiza...
Sessions and Context-Based Interaction
5. Front-End APIs for Context
 Map APIs to devices and manages interactive sessions
 Ask for additional details before c...
Edge Computing
http://www.businessinsider.com/internet-of-things-cloud-computing-2016-10
Edge Computing with NAS
AWS Snowball Edge
+ AWS Greengrass
6. On-Device APIs
 One interface, multiple implementations
 Store-and-forward strategy with
synchronization when offline...
Bots
Slack Chatbot Interaction
7. Bots as Next Generation APIs
 Currently, the assumption is that bots are talking
to humans
 But, what if our apps cou...
API Design Is Changing
1. Hypermedia and
HATEOAS
2. Event subscriptions
3. Capability-driven API
design
4. Content negotia...
The Road Ahead
1990s
Distributed
Object Integration
2000s
Corp-to-Corp
Integration
2010s
+
Mobile/Data
Integration
2020s
?...
James Higginbotham
james@launchany.com
@launchany
https://apideveloperweekly.com
Thank you
APIStrat 2017: API Design in the Age of Bots, IoT, and Voice
Upcoming SlideShare
Loading in …5
×

APIStrat 2017: API Design in the Age of Bots, IoT, and Voice

1,062 views

Published on

Our API design should be user-first: a reflection of the kinds of capabilities and outcomes our users expect. New devices and software interaction will change the way we design web APIs. Presented at APIStrat 2017

Published in: Software
  • Be the first to comment

APIStrat 2017: API Design in the Age of Bots, IoT, and Voice

  1. 1. API Design in the Age of Bots, IoT, and Voice James Higginbotham @launchany https://apideveloperweekly.com
  2. 2. The Road So Far… 1990s Distributed Object Integration 2000s Corp-to-Corp Integration 2010s + Mobile/Data Integration
  3. 3. The State of API Design in 2017
  4. 4. APIs are stuck in the land of CRUD
  5. 5. API Conversations with CRUD
  6. 6. API Design is an architectural concern that combines business, product design, and technology
  7. 7. Messaging Platforms
  8. 8. When APIs Meet Jobs-To-Be-Done
  9. 9. 1. Hypermedia and HATEOAS (again)
  10. 10. Choose Your Own Adventure for APIs
  11. 11. When APIs Meet Jobs-To-Be-Done { … "_links": { “self": {"href": "/approval-requests/d796f2d0eb72492bb088"}, “approve": {"href": "/approval-requests/d796f2d0eb72492bb088/approve"}, “decline": {"href": "/approval-requests/d796f2d0eb72492bb088/decline"}, }, … }
  12. 12. 2. Event Subscriptions
  13. 13. https://www.asyncapi.com/
  14. 14. 1_Blank
  15. 15. IoT
  16. 16. Common Alexa Commands
  17. 17. 3. User-First, Capability-Driven API Design
  18. 18. Visual Voice
  19. 19. GET https://api.myexample.com/projects Accept: application/json;q=0.5,text/html;q=1.0 4. Content Negotiation For Visualization HTTP/1.0 200 OK Date: Tue, 16 June 2015 06:57:43 GMT Content-Type: text/html <html>…</html>
  20. 20. Sessions and Context-Based Interaction
  21. 21. 5. Front-End APIs for Context  Map APIs to devices and manages interactive sessions  Ask for additional details before calling backend APIs  Adaptive to support optional context data (min, typical, max data input) { … "_links": { “self": {"href": "/sessions/d796f2d0eb72492"}, “accounts": {"href": "/ sessions/d796f2d0eb72492/accounts"}, “credit-lines": {"href": "/approval-requests/d796f2d0eb72492/credit-lines"}, }, … }
  22. 22. Edge Computing http://www.businessinsider.com/internet-of-things-cloud-computing-2016-10
  23. 23. Edge Computing with NAS
  24. 24. AWS Snowball Edge + AWS Greengrass
  25. 25. 6. On-Device APIs  One interface, multiple implementations  Store-and-forward strategy with synchronization when offline  Local API gateway and management  Monitoring and managing edge nodes goes beyond the data center
  26. 26. Bots
  27. 27. Slack Chatbot Interaction
  28. 28. 7. Bots as Next Generation APIs  Currently, the assumption is that bots are talking to humans  But, what if our apps could talk to bots as if it were an API?  What if natural language is better for some APIs?  What if a hybrid language is necessary to support next gen API integration?
  29. 29. API Design Is Changing 1. Hypermedia and HATEOAS 2. Event subscriptions 3. Capability-driven API design 4. Content negotiation 5. Front-end context APIs 6. On-device APIs 7. Bots as next generation APIs
  30. 30. The Road Ahead 1990s Distributed Object Integration 2000s Corp-to-Corp Integration 2010s + Mobile/Data Integration 2020s ? Capability Integration
  31. 31. James Higginbotham james@launchany.com @launchany https://apideveloperweekly.com Thank you

×