yottamusic
The business, the turning points, and the decisions behind them.
01 / WHAT IT BUILT
What the company did
YottaMusic was a slick third-party web client for the Rhapsody subscription music service. Built by a developer known as Luke, it let Rhapsody subscribers play their music through a web browser — notably on Macs and across multiple computers — improving on Rhapsody's own clunky web-based player. It gained a loyal following among music bloggers and Rhapsody users before it was shut down in January 2008 at Rhapsody's request.
02 / yottamusic FAILURE REASONS
Failure reasons
YottaMusic was built on Rhapsody's DNA APIs, including undocumented interfaces that founder Luke had been given access to. When Rhapsody changed its mind about supporting those undocumented APIs, the web client's foundation disappeared overnight and the service had to close. It was a textbook platform-dependency failure: the product's existence rested entirely on a platform owner's continued permission, and that permission was revoked. Contemporary observers noted it was a loss for Rhapsody's own developer ecosystem, since YottaMusic had made the paid service more usable and promoted it. This concerns the specific API-dependency risk, not third-party music clients in general.
03 / EVENT HISTORY
Events in the structured record
- Closure announced
In January 2008, YottaMusic shuts down at Rhapsody's request after the company withdraws support for the undocumented APIs the web client was built on.
04 / CONTEMPORARY REBUILD ASSESSMENT
Difficulty of rebuilding this project today
Material for this section is being gathered and checked. It will appear here once ready.
Overall assessment: Not completed
05 / CAUSAL CHAIN
How the factors connect
- 01
Slick third-party web client for Rhapsody subscribers
- 02
Built on Rhapsody's DNA APIs, including undocumented ones
- 03
Rhapsody changes course and withdraws API support
- 04
January 2008: forced to shut down