Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.
Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.
Published on
While chatbots (what some people are calling “invisible apps”) have existed for some time, it’s only recently that the world seems to have gone bot crazy. The proliferation of third-party API companies is fundamentally changing the dynamics of how software is created and brought to market and chatbots are witnessing this huge paradigm shift.
In fact, these type of apps are basically entirely API-driven and event driven. As the number of services that expose APIs grows, the number of ways to combine them increases exponentially, and we’re just at the very beginning. The dream of easily reusable components is an old one in programming, but only today we find the required components have arrived in full force.
So how are API enabling the chatbot craze? What are the requirements for an API to fit into this landscape? What are the tools out there that are enabling this API-glue approach?
Login to see the comments