This is the API deck I prepared but didn't use at our iMA session on Moving Beyond the Website. Instead, we went free-form.

1. How did we end up
here?
Javaun Moradi, NPR
@javaun

2. Public radio’s evolutionary branches
TEXT
2007
Websites,
blogs,
2000’s multimedia,
Websites text 2010
LJCs
expands 2009 Responsive begins
Mobile apps &
mobile sites
1990’s explode
Basic sites: 2008
Rundowns, NPR API
Audio streams.
2011 2012
Infinite Player Connected cars
2005 2008
Podcasting Public Radio Player
AUDIO 2006
PRX Exchange

3. Public radio’s evolutionary branches
TEXT
2007
Websites,
blogs,
2000’s multimedia,
Websites text 2010
LJCs
expands 2009 Responsive begins
Mobile apps &
mobile sites
1990’s explode
Basic sites: 2008
Rundowns, NPR API
Audio streams.
2011 2012
Infinite Player Connected cars
2005 2008
Podcasting Public Radio Player
AUDIO 2006
PRX Exchange

4. Escape to mobile. App or site?
(C) XKCD http://xkcd.com/1174/

5. Responsive is a good place to start

6. How much text do we need?

7. What is public
radio best at?

8. 1971
2004
1974 2008
1995
1975 1995

10. We've never beaten this. Someone will.

11. Think like software companies
• Bezos: this is a software company. We make
money shipping boxes
• Jobs: this is a software company

12. Software companies make great
products

13. Software isn’t just distribution and packaging

14. Software *is* the product. (And it sells)
• UX and design experience
o Intuitive, convenient, fast
o Rich features
• User identity and history
o Take my preferences with me
• Data science
o What should we recommend?
o When should we ask for money?

15. How will audio storytelling change?

16. NPR API Update

17. Last year’s API ground work
• Content permissions
• Station data & schedules
• Self-service docs
• Moving towards the PMP
• Digital Services >100 stations in the API
•

18. API integration doesn’t have to be hard
• Core Publisher
• > 100 stations
• Fully supported
• Responsive mobile site
• API ingest/retrieval, out of the box
• CDN audio hosting

19. Self-service tools

20. This year’s focus
• PMP
• Local station presence & support
• Mobile audio and next gen listening support

21. PMP core needs
• Fast!
• Scalable to support the whole system
• Permissions & controls
• Neutral: not tied to rigid data scheme or CMS
• Interoperable: some things we all understand
• Flexible: support individual producer data

22. Taxonomies - how little do we need?

23. APIs Now

24. APIs are changing

25. The PMP Tomorrow?

26. We need local audio!
• Local newscast without times and traffic
• Local segment audio
(We know this is hard. We’re working on it too.)