Posted on 09-18-2012
I’m currently processing several discussion I’ve had with folks about APIs and the future of search when it comes to voice enabled apps, like Apple’s Siri.
It started with a discussion with the Webshell folks about their blog post, Webservices supply chain management : the SIRI case. Next I was reading a presentation from Pat Cappelaere(@cappelaere) CEO of Vightel Corporation. called Building Tomorrow’s Web Services API.
Pat has an interesting image in his deck, showing who the next generation consumer of your API will be:
These conversations reflect a whole new area of consideration for the future of web APIs. Will voice be the dominant way to search via our mobile devices? If so, how do we expose our companies resources, in a way that makes them easily consumed by voice enabled apps?
At the simplest, we need to discuss where REST fails us in this scenario, and at the most complex we need to discuss what “activities” will be consumed by voice apps and what types of “supply chain management” processes or framework will we need to manage all of this.
All of this will feed into to whether or not your company, its products and services will be found in a Siri-like search, when voice enabled apps become the default.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- Swagger Visualization Layer Using D3.js
- Establishing Common Dictionaries That Industries Can Use In Their API Design
- Top 5 Most Popular Themes On API Evangelist In 2014
- Query Parameter Determining Which Fields Are Queried For API Call
- Now Our Development Environment Is Now Containerized And Scalable Like Our Production Environment
- Guest Post: Let Our Sponsors Blow A Little Smoke Up Your Ass
- API Discovery Continues Its Move Into The IDE With Eclipse Che
- Evolving Beyond Just Resources Towards A More Experience Based API Design
- Another View of The API vs. Data Download Model
- If You Have A Publicly Available Mobile App You Have a Public API