Upgrade to Pro — share decks privately, control downloads, hide ads and more …

An API for drinks: And the innovation that foll...

An API for drinks: And the innovation that followed

Eva Sjökvist, Absolut Vodka
Keynote
API Strategy & Practice Conference, Amsterdam 2014

More Decks by API Strategy & Practice Conference

Other Decks in Technology

Transcript

  1. • Where we came from • What we set out

    to do • What we learned • How we created 3500 How to mix movies Constructing the world first API for drinks and the innovation that followed.
  2. To help consumers get the most enjoyment out of our

    products we need to ensure top quality drinks and recipes are consistently delivered regardless of where consumers encounter Absolut. We sell vodka. But people drink drinks.
  3. Since the first iPhone, consumers were more and more inclined

    to use new services. ! We were the first ever spirits brand in the Appstore. ! A shifting consumer landscape
  4. 8 An eco-system that was crowded ! And this was

    2011 We were all over the place, or at least in all the app-stores. Over time we realised that having multiple apps relying on different technologies were time consuming to manage.
  5. We realised by looking beyond the flavour of the months

    that we had a type of resource that could be extended to other outlets, contexts and devices. The assets could easily be extendable
  6. 1 Objectives ! • Lower Time To Market and cost

    for new devices ! • Tech stability and control ! • Streamline assets globally 2 Considerations ! • Look beyond flavour of the month. • Look beyond the latest campaign. • Win our markets and consumers. 3 Key to our consumers ! • “I have no idea what to make” • “I have no idea what to order” We wanted a tech backbone that could connect the dots. Opening up our assets
  7. Creation of a sound data model Imagining all things possible

    to do with a drink. ! Stir, Strain, Muddle, Float, Add, Pour, Garnish 14
  8. 18 Getting technology right Rest API Raven DB database Drink

    system that holds all the logic and the data model. Changing all clients to read from Api
  9. Key Takeouts ! - Formerly, we had data. Now we

    know and own the data. ! - Moving knowledge in-house enables product ownership in an agile methodology ! - We definitely see a change internally that gives more credit to open collaboration and external innovation. ! - Standardising the assets lead to technical creativity.
  10. Being in the spirits business, having a completely open api

    is challenging. ! That said, we are currently working on a full API-license. Where we want to go from here