Downloaded 58 times
Uploaded byBruno Pedro
Who's using your API?
This document discusses strategies for API providers to better engage with customers. It notes that companies should focus on capabilities rather than saying "API" and that the customer experience is shaped by how others use the API. The document evaluates pros and cons of the traditional API model and suggests alternatives like paid solutions, integrations, and ready-to-use options to give API providers more control over the customer experience.
More Related Content
![[Startup Nations Summit 2014] Competition - China - Beijing](https://cdn.slidesharecdn.com/ss_thumbnails/presentation-141004042145-conversion-gate02-thumbnail.jpg?width=640&height=640&fit=bounds)
![Getting Started with Apache Spark: Big Data Made Simple [Free Meetup]](https://cdn.slidesharecdn.com/ss_thumbnails/apachesparkgettingstarted-260203175547-8361bcc3-thumbnail.jpg?width=640&height=640&fit=bounds)
Who's using your API?
- 1. http://www.flickr.com/photos/jamescridland/613445810/ Who’s using yourAPI? Bruno Pedro 22 February 2013
- 2. Bruno Pedro Web andCloud Computing Technologist with over ten years’ experience. CTO of Nubera, the company behind GetApp and CloudWork. http://brunopedro.com/
- 3. Companies that surviveare the ones that are obsessed with customer experience. —Jeff Lawson, CEO twilio
- 4. Engage your customer: don’tsay API, say Capability. —Laura Merling, AT&T
- 5. So, who areyour customers? How do you reach them?
- 6. Your API features Traditional API developers distribution channel 1001101001001000 0011010010110100 applications Your customers
- 7. Pros • Decoupled appdevelopment Your company API
- 8. Pros • Engaging developercommunity
- 9. Pros • If doneright, exponentially scalable
- 10. Cons • Loss ofcontrol over final product • Poor or non-existant customer support • Only successful if it scales quickly
- 11. Your customer experienceis controlled by someone else!
- 12. Alternatives? • Customers payfor solutions • APIs work better together • Offer ready-to-use integrations
- 13. Your API integrations 1001101001001000 0011010010110100
- 15.
- 16.
- 17. Integrations • Marketing throughtraditional channels
- 18. Multiple API Your API distribution channels features integrations developers 1001101001001000 0011010010110100 self-service catalog applications Your customers
- 19. Benefits • Multiple distributionchannels • Co-marketing with other app vendors • Overall better customer experience!
- 20. So, who areyour customers? How do you reach them?
- 21. http://www.flickr.com/photos/jamescridland/613445810/ Who’s using yourAPI? Bruno Pedro 22 February 2013