how did we end up here? moving beyond the website, ima 2013

How did we end up here?

Javaun Moradi, NPR@javaun

Public radio’s evolutionary branches

1990’sBasic sites:Rundowns,Audio streams.

2000’sWebsites text expands

2006PRX Exchange

AUDIO

TEXT2007 Websites, blogs, multimedia, LJCs

2008 Public Radio Player

2008NPR API

2009Mobile apps & mobile sites explode

2011Infinite Player

2010Responsive begins

2012Connected cars

2005Podcasting

Public radio’s evolutionary branches

1990’sBasic sites:Rundowns,Audio streams.

2000’sWebsites text expands

2006PRX Exchange

AUDIO

TEXT2007 Websites, blogs, multimedia, LJCs

2008 Public Radio Player

2008NPR API

2009Mobile apps & mobile sites explode

2011Infinite Player

2010Responsive begins

2012Connected cars

2005Podcasting

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 public radio best at?

1971

1995

2004

20081974

1975

1995

We've never beaten this. Someone will.

Think like software companies

• Bezos: this is a software company. We make money shipping boxes

• Jobs: this is a software company

Software companies make great products

Software isn’t just distribution and packaging

Software *is* the product. (And it sells)

• UX and design experienceo Intuitive, convenient, fasto Rich features

• User identity and historyo Take my preferences with me

• Data scienceo What should we recommend?o When should we ask for money?

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

• Digital Services >100 stations in the API•

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

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 scheme or CMS

• Interoperable: some things we all understand

• Flexible: support individual producer data

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 it too.)