How did we end up      here?Javaun Moradi, NPR@javaun
Public radio’s evolutionary branchesTEXT                             2007                             Websites,           ...
Public radio’s evolutionary branchesTEXT                             2007                             Websites,           ...
Escape to mobile. App or site?      (C) XKCD http://xkcd.com/1174/
Responsive is a good place to start
How much text do we need?
What is publicradio best at?
1971                               20041974                                  2008                        1995          197...
Weve never beaten this. Someone will.
Think like software companies• Bezos: this is a software company. We make    money shipping boxes•   Jobs: this is a softw...
Software companies make great          products
Software isn’t just distribution and packaging
Software *is* the product. (And it sells)• UX and design experience  o Intuitive, convenient, fast  o Rich features• User ...
How will audio storytelling change?
NPR API Update
Last year’s API ground work• Content permissions• Station data & schedules• Self-service docs• Moving towards the PMP• Dig...
API integration doesn’t have to be hard•   Core Publisher•   > 100 stations•   Fully supported•   Responsive mobile site• ...
Self-service tools
This year’s focus• PMP• Local station presence & support• Mobile audio and next gen listening support
PMP core needs• Fast!• Scalable to support the whole system• Permissions & controls• Neutral: not tied to rigid data schem...
Taxonomies - how little do we need?
APIs Now
APIs are changing
The PMP Tomorrow?
We need local audio!• Local newscast without times and traffic• Local segment audio(We know this is hard. We’re working on...
How did we end up here? Moving beyond the website, iMA 2013
Upcoming SlideShare
Loading in...5
×

How did we end up here? Moving beyond the website, iMA 2013

409

Published on

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.

Published in: Technology
1 Comment
0 Likes
Statistics
Notes
  • Be the first to like this

No Downloads
Views
Total Views
409
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
2
Comments
1
Likes
0
Embeds 0
No embeds

No notes for slide

How did we end up here? Moving beyond the website, iMA 2013

  1. 1. How did we end up here?Javaun Moradi, NPR@javaun
  2. 2. Public radio’s evolutionary branchesTEXT 2007 Websites, blogs, 2000’s multimedia, Websites text 2010 LJCs expands 2009 Responsive begins Mobile apps & mobile sites1990’s explodeBasic sites: 2008Rundowns, NPR APIAudio streams. 2011 2012 Infinite Player Connected cars 2005 2008 Podcasting Public Radio PlayerAUDIO 2006 PRX Exchange
  3. 3. Public radio’s evolutionary branchesTEXT 2007 Websites, blogs, 2000’s multimedia, Websites text 2010 LJCs expands 2009 Responsive begins Mobile apps & mobile sites1990’s explodeBasic sites: 2008Rundowns, NPR APIAudio streams. 2011 2012 Infinite Player Connected cars 2005 2008 Podcasting Public Radio PlayerAUDIO 2006 PRX Exchange
  4. 4. Escape to mobile. App or site? (C) XKCD http://xkcd.com/1174/
  5. 5. Responsive is a good place to start
  6. 6. How much text do we need?
  7. 7. What is publicradio best at?
  8. 8. 1971 20041974 2008 1995 1975 1995
  9. 9. Weve never beaten this. Someone will.
  10. 10. Think like software companies• Bezos: this is a software company. We make money shipping boxes• Jobs: this is a software company
  11. 11. Software companies make great products
  12. 12. Software isn’t just distribution and packaging
  13. 13. 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?
  14. 14. How will audio storytelling change?
  15. 15. NPR API Update
  16. 16. 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•
  17. 17. 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
  18. 18. Self-service tools
  19. 19. This year’s focus• PMP• Local station presence & support• Mobile audio and next gen listening support
  20. 20. 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
  21. 21. Taxonomies - how little do we need?
  22. 22. APIs Now
  23. 23. APIs are changing
  24. 24. The PMP Tomorrow?
  25. 25. We need local audio!• Local newscast without times and traffic• Local segment audio(We know this is hard. We’re working on it too.)
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×