Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.

"How to create an efficient API.. with a business model?" by Nicolas Grenié

1.616 visualizaciones

Publicado el

A common mistake when discussing API business models is to think of the API first. But everyone should consider how an API will interact with a business model.

We will answer to the following questions:
What is an API? Which business model can you include in an API? How to use the canvas model to build a badass API?

Nicolas Grenié is a Hacker in Residence at 3scale living between Barcelona and San Francisco. He built his first website in 2000 using Microsoft Word, and since them did not stop learning about programming. Nicolas likes to try new languages all the time, so he has experience in PHP, Ruby and Node. When not working you have a good chance to find him hacking on side projects or enjoying a good craft beer. And of course, as he is French, frog and snails are part of his daily diet!

Publicado en: Empresariales

"How to create an efficient API.. with a business model?" by Nicolas Grenié

  1. 1. HOW TO CREATE AN EFFICIENT API…WITH A BUSINESS ? #TFWORKSHOP
  2. 2. TheFamily 
 code: lamifasisi WIFIWIFI
  3. 3. DISAGREE ON TWITTER! #TFWORKSHOP
  4. 4. #TFWORKSHOP NICOLAS GRENIÉ HACKER IN RESIDENCE AT 3SCALE @PICSOUNG HOW AN API WILL INTERACT WITH A BUSINESS MODEL?
  5. 5. An efficient API program... with a business model? TheFamily Paris, Dec. 11, 2015 Nicolas Grenié @picsoung Hacker in Residence at 3scale.net
  6. 6. @picsoung 3scale.net/jobs
  7. 7. @picsoung 700+ clients worldwide billions of API calls per month
  8. 8. @picsoung @picsoung
  9. 9. You YouR API
  10. 10. EXtra Revenues
  11. 11. EXtra Revenues ✴QuickPrint API, 13x partner growth ✴Revenue share with developers ✴Apps using SDK on top charts ✴Increase in foot traffic in stores source: http://www.slideshare.net/apigee/the-walgreens-story-putting-an-api-around-their-stores
  12. 12. Wider Reach
  13. 13. Wider Reach ✴700 partners created 50,000 third party apps/services ✴300m monthly uniques who see the brand on other sites ✴The API gave reach and brand awareness which would not have been possible with tr marketing. 
 (Dick Brouwer, TripAdvisor Director of Engineering)
  14. 14. Wider Reach
  15. 15. Innovation
  16. 16. Innovation ✴Only 1 app developed by Fitbit in-house ✴Third party apps in Fitbit’s ecosystem accumulated are worth $1m of development cost ✴Powerful to be on many platforms easily Source: http://www.slideshare.net/faberNovel/why-shouldicareaboutap-is4/53
  17. 17. Efficiency
  18. 18. Efficiency ✴Wrap every internal service with an API – or you are fired ✴Better re-usability, quicker integration, spot opportunities, get to market quicker (AWS) Source: http://apievangelist.com/2012/01/12/the-secret-to-amazons-success-internal-apis/
  19. 19. ! mobile " customer eco-system # partner eco-system $ content distribution % API as a Business & An API DIFFERENT GOAL
  20. 20. @picsoung The problem
  21. 21. @picsoung APIs are becoming mainstream
  22. 22. @picsoung API programs are going beyond just technical
  23. 23. @picsoung API programs are part of the organization strategy
  24. 24. @picsoung API programs involve more diverse teams and user profiles
  25. 25. @picsoung What is an API program?
  26. 26. @picsoung all elements necessary to describe deliver capitalize the value of the API
  27. 27. @picsoung Capitalization Delivery Value
  28. 28. @picsoung Analogy: Business Model Canvas
  29. 29. @picsoung source: www.businessmodelgeneration.com
  30. 30. @picsoung Business Model Canvas API Model Canvas
  31. 31. @picsoung API Model Canvas
  32. 32. @picsoung
  33. 33. @picsoung The infrastructure and ressources The
 (technical)
 API
 itself The Customer = Developer Value for money
  34. 34. @picsoung The
 (technical)
 API
 itself
  35. 35. @picsoung
  36. 36. @picsoung The infrastructure and ressources The
 (technical)
 API
 itself
  37. 37. @picsoung
  38. 38. @picsoung The infrastructure and ressources The
 (technical)
 API
 itself The Customer = Developer
  39. 39. @picsoung
  40. 40. @picsoung The infrastructure and ressources The
 (technical)
 API
 itself The Customer = Developer Value for money
  41. 41. @picsoung
  42. 42. @picsoung On each field •Into/context •Important questions (checklist) •Further resources
  43. 43. @picsoung Demohttp://bit.ly/APImodelCanvas
  44. 44. @picsoung Next on API model Canvas •user testing and validation •more interactive site •team collaboration •extension of the method
  45. 45. @picsoung Value Proposition Canvas source: www.businessmodelgeneration.com
  46. 46. @picsoung Value Proposition Canvas source: www.businessmodelgeneration.com
  47. 47. @picsoung Using the Value Proposition Canvas 1.Describe the user jobs, pain points, gains. 2.Describe the main API features, pain relievers, and gain creators. 3.Define “fit statements.” If you cannot find any, refine the API. 4.Summary of the fit statements is the value proposition.
  48. 48. @picsoung Example:
 MusicGraph API
  49. 49. API as a growth tool Nicolas Grenié @picsoung Hacker in Residence at 3scale.net @3scale TheFamily Paris, Dec. 11, 2015
  50. 50. SEE YOU SOON! 
 LOVE. THEFAMILY.CO
 ___

×