As the media leader who first brought a public content API to the market in 2008, NPR continues to innovate and learn about what it means to have flexible content. Our philosophy assumes that to maintain relevancy in an online world media companies need to be adroit at delivering content to multiple channels and disparate platforms. This in turn has lead us to keep a strategic focus on our API development. This positions us not just to meet our distribution needs, but has also helped drive business opportunity and allows for effective design and user experience whether in a browser or on a mobile device. This presentation will share our lessons learned and key metrics around successful creation and use of flexible content – from technology needs to business, editorial and design opportunities in an increasingly fragmented online product landscape.

2. “ From NPR News in Washington..” –Jack Speer et al

3. “ From NPR News in Washington..” –Jack Speer et al X 35M / Week X 784

5. NPR Digital Media API

6. So Why Should YOU Care about Flexible Content?

7. A) Staying Relevant Is Getting Much Harder Step 1 Step 2 You

8. 0 - 50 > 1,000,000,000 > 800,000

9. B) It’s Worked Well For Us… NPR News iPhone app NPR News Android app Relaunched NPR mobile site NPR iPad app NPR Music iPhone app API launched in 2008, at OSCON NPR Music Remix NPR Blogs Made API Friendly Facebook Integration Player 2.0 Homepage Improvements Story Page Improvements

11. Good Tools Good People Good Content

21. “ Learning a slew of technical skills isn't the answer, it's just part of the journalism equation.” - http://10000words.net/

23. “ From Washington DC… this is NPR”

26. NPR Addict iPhone App

29. System Architecture Supporting COPE

30. System Architecture Supporting COPE

31. System Architecture Supporting COPE Java JSP Struts

32. System Architecture Supporting COPE R / W MySQL

33. System Architecture Supporting COPE R / O MySQL Cluster NoSQL-like XML Repository

34. System Architecture Supporting COPE PHP5 SimpleXML PHP5

35. Inside the API’s “Black Box”

36. Life and Times of Flexible Content

37. NPR CMS

38. NPR API

39. NPR.org

40. HTML5 / Tablet Site

41. NPR.org Audio Player

42. iPhone App Android App Mobile Site

43. Google Chrome Extension

44. iGoogle Gadget

45. KQED.org

46. WBUR.org

47. Connecticut Public Broadcasting Photos Courtesy Derik Elis, CBTV NPR API CPTV’s Drupal Based CMS Website

48. What We Learned

49. “ I had to actually purchase a book to learn the API and write the client.” Shawn Fanning of Napster Fame

50. Yeah, About That Chart…. Figuring it out… Election Related Traffic Bumps

51. Station Content in the NPR API (today)

52. KLCC Displaying N3 Stories from NPR API

53. WBUR Displaying N3 Story from NPR API

58. A thousand words of COPE

61. Make it ALL reusable

63. API Keys and Consumption by Audience

64. Output Format Distribution This distribution chart is from June 2009 and does not include NPR consumption. We believe the distribution still applies today.

65. Page Views to NPR Tech Center

66. NPR Story API : Requests per Month > 20 requests to the Story API every second

68. NPR Android App http://code.google.com/p/npr-android-app/

69. What’s Next (or at least still causing us problems)

70. Station Content in the NPR API (today)

71. Public Media API (future)