Dimitrios Tydeas Mengidis Taxibeat
Building API for an existing application or applying “API first” development, I have found myself designing API from a misleading perspective. Focused on solving the problem, soon the concerns of the caller were quickly forgotten. Misunderstanding the purpose of an API ended up giving our consumers a bad time. An API should be designed from the perspective of the caller. A Hypermedia design can empower the product “value” delivered within the API and approximate the value a user, who interacts with a UI, gets. During this presentation I would like to touch on the subject of common pitfalls that lead us to design an API from the wrong perspective, to reference types of our potential clients and provide examples on how hypermedia could help us honor our business.
This post is older than 4 years. External links has been removed
October 21, 2014 15:50
High impact blog posts and eBooks on API business models, and tech advice
Connect with market leading platform creators at our events
Join a helpful community of API practitioners
Can't make it to the event? Signup to the Nordic APIs newsletter for quality content. High
impact blog posts on API business models and tech advice.
Become a part of the world’s largest community of API practitioners and enthusiasts. Share your insights on the blog, speak at an event or exhibit at our conferences and create new business relationships with decision makers and top influencers responsible for API solutions.