Before and after: Why did Sveriges Radio think we needed an open API
summary
A public broadcaster starts with screen‑scraped program lists (2007), replaces them with generated XML and RSS feeds as API, and powers an iPhone app that exposes the endpoints to outsiders; a community Android client prompts the first official API launch at Music Hack Day 2010. License confusion forces a 2012 redesign into a versioned API with lifecycle, a user group, and v2 that external apps (notably Replay iPad app integrating Twitter) adopt while internal apps migrate and uncover performance issues; planned v3 is postponed for budget reasons.
AI-written summary · about
chapters (13)
- 0:00Open API journey
- 1:07Screen scraping and XML files
- 2:36RSS feeds and iPhone app
- 4:43Android community and API launch
- 6:10Legal concerns and licensing
- 8:41General API development
- 10:28Version 2.0 and collaboration
- 11:52Content licensing challenges
- 13:40API version 2.0 launch
- 15:07API versioning benefits
- 16:12Version 3.0 plans and budget
- 17:40User license agreements future
- 19:07Q&A
related talks
19mAPIs in the media industry: models and trends for 2019
21mAPI's - a Part Of the Creative Pallet
12mA Conversation with Ryan Sarver
13mAPIs in the public transport industry — what's next?
21mThe power of unexpected APIs
18mIn Which Extent are APIs a Strategic Tool for a Global News Agency?
26mFrom project to reality let's explore some API
26mAPIs as Agent of Change