The reality is that NPR, stations, and partners were almost all of the usage.
This is not an authoritative depiction of where these APIs live, it’s an exercise I used to think about where our APIs should live and how much resources/time should go into each area.
The space is really nascent. We don’t know where it’s going to go. It is critical to our business and we want to be in full control of our roadmap. It’s our core technology, we’re invested.
The Who, What, Where, When, Why, and How of APIs
TheWHO, WHAT, WHERE, WHEN, WHY, HOW* of Building APIs… (* not in that order) Javaun Moradi, NPR @javaun
(This slide isn’t a “W” or “H”)• NPR Open API launched in 2008• Try it: http://dev.npr.org or Codecademy.com• Powers all of NPR’s mobile, web, cars apps• 100+ stations retrieve content & add their own
(Last background slide for a while)NPR’s APIs• Stories• Stations• Schedules• Streams• Library data• Transcripts• …
APIs are about the opportunities you don’t miss.
WHY do we love APIs?• Keep pace with your product needs• Innovate quickly• Reuse, don’t reinvent• Serendipity
WHEN is it time to get an API?• Mobile aspirations?• Data/services useful in more than one place?• Departments need to share/collaborate?• Decouple your systems?• Be more nimble?• Share your service (free or for profit)?