The APIs of Me - Virtualizing Channels and Devices
Download as PPTX, PDF1 like481 views
The document discusses the evolution of API strategies in modern businesses, particularly focusing on how companies like Pearson and Walgreens are utilizing APIs to enhance digital transformation and bridge gaps in technology use among students and customers. It emphasizes the importance of simplifying access to APIs to unlock creativity, improve connections between apps and devices, and enhance user experiences. The document also highlights successful implementations of APIs within Walgreens, showcasing various integrations that streamline customer interactions and drive innovation.
The APIs of Me - Virtualizing Channels and Devices
- 1. 1 The APIs of Me - Virtualizing Channels and Devices Ed Anuff, Apigee Allen Rodgers, Pearson Drew Schweinfurth, Walgreens
- 2. Digital Transformation Meets Traditional Business 2 Source: Gartner - CEOs and CIOs Must Assume That Every Industry Will Be Digitally Remastered, 2014, Raskino
- 3. Single-Channel Multi-Channel Omni-Channel 1990 Today Digital Has Remade Channel Strategies
- 4. B2D Powers B2C, B2B and B2E APIs turn into products and Developers transform into clients: Developer Internal API Partner API Open API INTEGRATION COLLABORATION INNOVATIONAPIs APIs Link The New Value Chains
- 5. How can today’s business operationalize APIs to drive new channel strategies? 5©2015 Apigee. All Rights Reserved.
- 6. Let’s hear from the front lines… 6©2015 Apigee. All Rights Reserved.
- 7. 7
- 8. API of Me - Bridging the Gap Allen Rodgers Director, Pearson API Program 8
- 9. About Us Welcome to Pearson. We have a simple mission: to help people make more of their lives through learning worlds largest education company1 with 40,000 employees2 More than 70 countries3
- 10. 10
- 11. ? Agenda 11©2015 Apigee. All Rights Reserved. Current State ObservationsInnovation Hypothesis Closing the GapQuestion
- 12. Current State 12
- 13. How ARE We defining Success, and exploring exploring Opportunities 300 Active Partners 1 30 + Apps 2 300 + Integrations 3 Successful! But… 4 The Program Today
- 14. Mobile yes! But…
- 15. But… what about the rest
- 17. Students' Mobile Learning Practices Source: Educause
- 18. Number of Ed Apps Source: Pocket Gamer
- 19. Student Use of Mobile Devices Source: Educause
- 20. Technical Challenge's Hard science and engineering degrees as a percent of all degrees Source: Wall Street Journal Only 5% in Computer Scien
- 22. How ARE We defining Success, and exploring exploring Opportunities Learning is individualized 1 Students leverage familiar tools 2 Low threshold for change/complexity3 Technology is complex 4 our Observations
- 23. Hypothesis 23
- 24. Lots of APIs, Lots of Apps Huge Gap between Ideas and Execution 1 APIs are an enabler but only to a select few 2 Lots of Apps running a plethora of devices 3 Lot of ideas but very few know how to act of those ideas 4 Technology is complex for a majority of students our Hypothesis
- 25. 25©2015 Apigee. All Rights Reserved. • 2 5 A gap
- 27. How can we connect the dots, and lower the barriers Value of APIs should be available to everyone1 Take advantage of what's been done and what's available2 Simplify the path between Apps and Devices3 Reduce the Complexity of Technology4 How To close the gap
- 28. One idea connect Source: Zapier
- 29. Integrate once, use as you like
- 30. Evernote Email SMS Social Media Integrate once, use where you like
- 31. Truly connected • 3 1 • 3 1
- 33. The API of Me: Virtualizing Channels & Devices Drew Schweinfurth Developer Evangelist Walgreens Developer Program 33
- 34. Agenda 34©2015 Apigee. All Rights Reserved.
- 35. Walgreens Devices and Changes 35
- 36. 36©2015 Apigee. All Rights Reserved. 8,200 Corners of Happy & Healthy
- 37. We used to measure convenience in miles and minutes 37 ©2014 Walgreen Co. All rights reserved. Confidential and proprietary information. For internal use only.
- 38. Today, we measure distance in inches and instants 38 Mobile fundamentally changes the nature of retail convenience, placing new pressure on Walgreens to redefine convenience once again
- 39. We live in a mobile world, Walgreens has become mobile <1% mobile 3% mobile 13% mobile 35% mobile 51% mobile 2009 2010 2011 2012 2013 Mobile Traffic Share on Walgreens properties 2014 60% mobile © 2015 Walgreen Co. All rights reserved. developer.walgreens.com apibizdev@walgreens.com @WalgreensAPI
- 40. It’s more than channel shift, there’s massive value here © 2015 Walgreen Co. All rights reserved. developer.walgreens.com apibizdev@walgreens.com @WalgreensAPI
- 41. So…What’s your API Strategy 41
- 42. Three Strategic Pillars Reimagine Connect Extend 1 digital experiences to our stores Walgreens through mobile solutions our greatest assets to an innovative ecosystem 2 3 RBS, QP In-Store-Mode Clip2Card © 2015 Walgreen Co. All rights reserved. developer.walgreens.com apibizdev@walgreens.com @WalgreensAPI
- 43. Walgreens API: The Heart of “Extend” Awareness Traffic Innovation Revenue Photo Prints Rx RefillBalance Reward s Schedule r © 2015 Walgreen Co. All rights reserved. developer.walgreens.com apibizdev@walgreens.com @WalgreensAPI
- 44. The initial shift, abruptly broke the internet © 2015 Walgreen Co. All rights reserved. developer.walgreens.com apibizdev@walgreens.com @WalgreensAPI
- 45. © 2015 Walgreen Co. All rights reserved. developer.walgreens.com apibizdev@walgreens.com @WalgreensAPI The Classic Photo Retail Business Model
- 46. © 2015 Walgreen Co. All rights reserved. developer.walgreens.com apibizdev@walgreens.com @WalgreensAPI The Renaissance Photo Retail Business Model
- 47. The Modern Photo Retail Business Model © 2015 Walgreen Co. All rights reserved. developer.walgreens.com apibizdev@walgreens.com @WalgreensAPI
- 48. 170+ integrations in 3 yrs Innovate and Incubate Embedded across all platforms © 2015 Walgreen Co. All rights reserved. developer.walgreens.com apibizdev@walgreens.com @WalgreensAPI The Granddaddy of them All: PHOTO PRINTS API
- 49. earn points for healthy activities, cash to spend in store connect a health tracking app/device register for Balance Rewards for healthy choices • 55+ total integrations in the last year • Popular apps like Lose It!, Misfit, RunKeeper & 7 Min Workout © 2015 Walgreen Co. All rights reserved. developer.walgreens.com apibizdev@walgreens.com @WalgreensAPI The Innovative little brother: Balance Rewards API
- 50. In the words of Bob Marley: “One Second, One Refill” © 2015 Walgreen Co. All rights reserved. developer.walgreens.com apibizdev@walgreens.com @WalgreensAPI Refill by Scan step 1 step 2 step 3 launch scan done!
- 51. The Eccentric older sister: Prescription API • Refill existing Walgreens or Duane Reade prescriptions • Transfer a prescription to Walgreens or Duane Reade • Top new integrations with Glow and WebMD © 2015 Walgreen Co. All rights reserved. developer.walgreens.com apibizdev@walgreens.com @WalgreensAPI
- 52. Reaching out + Touching Hands 52
- 53. Social Media, is the source of Communication © 2015 Walgreen Co. All rights reserved. developer.walgreens.com apibizdev@walgreens.com @WalgreensAPI
- 54. Developer Survey: Goodness 54 Program Rating: Availability Rating: © 2015 Walgreen Co. All rights reserved. developer.walgreens.com apibizdev@walgreens.com @WalgreensAPI “Keep up the great work guys!” “I did not find anything out of standards and Walgreens Developers were very helpful during integration process.” “Great support from the team and easy to get in touch with everyone via Basecamp.”
- 55. Developer Survey: Badness 55 Developer Portal Rating: Documentation Rating: Sample Code Rating: Errors Code Rating: © 2015 Walgreen Co. All rights reserved. developer.walgreens.com apibizdev@walgreens.com @WalgreensAPI “It would be also great to have a sandbox request/response area to execute sample requests on the fly.” “I received as a .pdf document. API documentation has all details, step-by-step implementation and request/response samples.” “In the documentation, all API endpoints given with a sample request code piece. Would be nice to see more languages.” “Depending on what type of error occurred and lack of standard error HTTP status codes made development challenging.”
- 56. Example of Mind blowing changes!
- 57. Questions? 57
- 59. Thank you