These are my live notes from the Netflix presentation at the Business of APIs conference.
Michael Hart - director of engineering at Netflix
Strategy:
API Goals
Enable Dvlpt of of Netflix experiences offsite
Leverage External developers, platforms, and users of platforms, ideas
Success Measured by:
- registered developers
- live applications
- subs engaging with netflix
new sub acquisitions
- subscriber delight
Partner Value Prop:
- Engagement with 8.7M subs
- association with a strong brand
- No ads. No pressure to drive traffic, as its is subscription business
- help partners make money - subscriber bounties
Design of API
Long tail of developers
- online support tools, developer registration, mashery helped
Enabling scale through design:
Simplicity - fastest ramp up, used REST, modeled around netflix catalogue, leveraged standards
Flixibility - wide range of functionality, technical javascript
Authority - about standards, avoding negotiation of terms, e.g Oauth
API Components
JavaScripti API
Rest API - developer controls ux
RSS and Atom Feeds
JavaScript API
Simplest API. embed netflix buttons
REST API
title search, ratings (read and write), subscriber activity, queue mgmt, previews (limited basis)
1612 registered users
197 active
mobile applications
one iphone app
amrtflicks for Blackberry
expect to get
Nice - gave rateitall props
LoveNetflix - dating site
Plaxo used javascript api and rest...
Lessons learned:
oauth is tough in the short term. It's a new standard.
good documentation isn't easy
APIs foster internal development too
What's next?
Application showcase
Opening up catalog access even more, may even lose authentication
More widgets (add and play today, add box art and stuff
Parting Thought
Put your data to work. (nice mention of a Sexy Widget post)
