BAPI San Francisco - 2013
Having just come back from Mashery’s BAPI 2013 in San Francisco, there’s one word that keeps popping in my head. Wow. I knew there were smart people in the world doing amazing things in the API space and I knew to expect great things from this conference, but I was really blown away.
Most of the time at various conferences, there are select agenda items that are can’t miss, and some that you can sneak out of and get to the lobby for some work time. At this year’s BAPI SFO, there wasn’t one presentation I wanted to miss. In fact, during some of the breakout sessions, I kind of wished I could clone myself like Jango Fett and sit in more than one at a time.
While I was lucky enough to attend, I don’t want you to miss out on anything so I’ve compiled my “Best of” summary below, in which I call out some of the key themes, or take-aways I had during each talk. I think there are some common threads amongst the presenters, and I’ll do my best to call them out below.
The day began with opening remarks from Oren Michaels, CEO of Mashery. We share the same hairstyle, so I was happy to see him up on stage proudly sporting the Bruce Willis look like I do.
What I took away from his talk was that in the 5th year of the conference, APIs are FINALLY starting to appear as a mainstream topic of how businesses can drive change, connectivity and transformation into their operations. He noted that there are now over 9,000 public APIs, and while it took over 3 years to hit the first 1,000 public APIs, the last 1,000 only took a matter of months. Adoption acceleration is happening. The tipping point, he said, was when APIs became not only read, but Read/Write.
Next Up: Eric Rodenbeck (@stamen)
Eric is an award winning data visualization expert. His theme was finding the unmarked trail. Basically, he said to “let your data lead you to the questions, don’t take a question and turn it into data”
To illustrate, take a look at what visualizing one day worth of Nasdaq trades look like:
What questions would you ask having seen this data? If given the choice of reviewing a spreadsheet or this chart, which one gave you a better chance of catching change as it happens?
Finally, he mentioned that we need to think about APIs differently. While they are machine language, what if we thought about APIs like novels? Could you say your API has a soul? Can it support new interactions or behaviors? What are the intentions? Is it interesting? Can I explore it? If I re-read it, will it seem as interesting as the first time around? Interesting angle to come at it….
The Next Big Thing: A panel discussion with John Sheehan, CEO of RunScope, Matt Brezina, CEO of Sincere.ly and Bastian Lehmann, CEO of Postmates
These guys talked at length about what it was like to run a startup, or multiple startups. Challenges faced by new people managers (Removing obstacles is the chief goal), the distractions that can take away focus from actually building an innovative product, the issues facing them as they scale their business.
It was an interesting conversation, and I found myself taking very few notes, opting instead to let myself absorb the conversation as it happened. I was impressed with the fortitude of these guys, and the vision they each demonstrated as they described the passion that they bring to their product on a daily basis.
Capital One Labs: Joshua Greenough, Sr. Director of Innovation
This was an interesting presentation, given that Joshua categorized his group as a “Rich Startup”. IE: backed by a big bank, and funded with an according budget. The stakes are just as high, but the risk of catastrophe sinking the initiative is much lower.
He talked at length about Design Thinking:
Empathize – Define – Ideate – Prototype – Test
He encouraged the idea of hackathons, and suggested that as a first step, look internal for inspirations, and work out the details before going external (if you do at all).
The other thing he touched on was the Golden Circle that placed “Why” at the center of every problem, followed by “How” and finally “What”. He encouraged us to start from the outside in vs from inside out.
His perspective: Inside out = Conventional. Outside in = Remarkable
His point: What is a tactical manifestation of Why
Finally, he took a moment to encourage everyone in the audience to watch this inspirational video by Simpon Sinek from Ted Talk 2010: http://www.ted.com/talks/simon_sinek_how_great_leaders_inspire_action.html
I watched it, you should too...:)
Daniel Jacobsen: The Evolution of the Netflix API
This was an interesting presentation from the company that essentially killed Blockbuster.
What Daniel talked about was how they evolved their API strategy from focusing on support existing developers, partner integrations and enabling devices in 2010, to maximizing efficiencies of internal developers, optimizing systems for rapid innovation, ensuring reliability and building scalable systems in 2013.
They view APIs as a tactic, not a strategy, which I agree with, and his story told of how they re-assessed how they wanted to bring their product to market, and how their pivot has enabled them to focus more energy on building the right things for all, vs building 100’s of things for everyone.
Note: In 2013, Netflix supported 41B calls, with 2B of those coming daily, and over 1,000 devices. Given their shift to supporting their API vs the hundreds of potential apps and devices, he noted that there were less than 1M external calls made last year.
Atticus Tyson – SVP Intuit
This was interesting, in that much of the presentation fociused on what Intuit was doing wrong, before they got it right. In 2010, Atticus inherited the final stage of a two year long implementation with their IT group, and Oracle. Once implemented, the system was deemed inadequate, and plans were laid to replace it. Yes, it made it uncomfortable for the people who designed and built the new system that was to be replaced, but kudos to them for immediately acting once they realized the system wouldn’t give them what they need. Too many times, people get defensive about the work, the investment, etc, leaving the end users to deal with a crippling tool.
Interestingly, Intuit uses NPS to rate the effectiveness of the API every quarter, and YOY. For them, here’s the scale:
0-6 = detractors
Proponants - Detractors = NPS. Thier target score is +50
John Musser Programmable Web / API Science; API Business Models
John Musser, the founder of ProgrammableWeb.com was up next. He talked about the changing API models out there today, and took us back to 2005 for a comparison point.
In 2005, there were basically four models:
2. Developer Pays
3. Developer gets paid
4. Indirect/Affiliate Program
Contrast that to 2013, where he calls out over 20 different models:
His main point was that the models are constantly changing. What you see in the picture above will look different in 6 months...maybe even 3 months!
Chris Moody – GNIP
GNIP is the largest provider of social data and social conversations. They gather their data from Facebook, twitter, tumblr, wordpress, instagram, you tube, disqus, G+, reddit, intense debate, bit.ly, stocktwits, flickr, vimeo and newsgator, primarily.
What Chris talked about can be summed up simply, and tied to the presentation by Eric Rodenbeck. The data is there, how do you see it? What would you do if you had access to it, and could react appropriately?
He shared an image of a reaction time grid, with twitter as the “fastest” response platform, and YouTube and tumblr as the “deepest”. Mining data from there can provide you with a quick read (fast), or some thoughtful comments to consider (deep).
Lynda Smith – Twilio; The Journey of the DOERs.
This presentation may have been the one I found myself most interested in. Lynda was a fantastically energetic presenter, and had a tight message for the participants.
First, some stats:
·Today, there are over 18.2M developers, which represents a 16% growth over 2012. Career counselors all over the country are getting it right.
·Today, 43% of companies have APIs, 5 years – 85% - venture beat.
·Their target = DOERs, are people who are excited about building something.
They break developers into four simple groups:
Linda also shared my favorite slide of the day…the Heirarchy of developers needs (the photo of the slide doesn't do it justice, here is the slide from VisionMobile.com.
And finally, she walked through their strategy for reaching the developer audience, creating a relationship with them, and earning credibility with them:
1. Enable them to find twilio – SEO/SEO
2. Go to where they are (hackathins)
3. Converse (github, twitter, other social)
4. Create opportunities to gather
5. Create a brand (track suits)
6. Build a great site
a. How it works (docs, how-to’s)
b. Clear pricing
c. Low friction to start (same problems we have, no idea who is doing what until they reach out)
Dr. Andrew Weigand – Former chief scientist for Amazon: Data Refineries
Dr. Weigand was one of the most engaging presenters of the day. He seemed to be a wicked smart guy who was able to provide some insight as to how Amazon views data, and what they do with it.
His talked summed up: Amazon refines data to help you make better decisions.
He says their whole goal is to make it easy to: Contribute, Connect, Collaborate
The types of data they look at to make recommendations include:
1. Manual (experts) > moved away from this, too labor intensive
2. Implicit (clicks, searches)
3. Explicit (reviews, lists)
4. Situation (local, mobile)
5. Social Graph (connections)
He finished up with a notation that Amazon got credit for changing the way people think about shopping, Google got credit for changing the way people think about searching, and Facebook changed the way people think about connections.
So that’s a wrap, I hope you enjoyed the recap, and I’d encourage you to visit any of the upcoming BAPI conferences if this type of thinking gets your gears going!
Thanks for reading.