Before You Build
Mobile AppShut Down

Rdio

Rdio was a polished music streaming service that shut down after its assets were sold to Pandora during bankruptcy proceedings.

View original story

Product snapshot

What it was

Rdio let users stream music on demand, create playlists, listen to stations, and discover music through web and mobile apps.

Who it was for

music streamersmobile music listenersplaylist and album listenerssocial music discovery users

Problem / value

Provide a polished subscription music experience with broad catalog access across devices.

Core workflow

Users searched for artists or albums, streamed tracks, followed playlists or stations, and built a personal listening collection.

Core dependency

The business needed licensed catalog access, retention, and distribution scale strong enough to compete with larger platforms.

Product form

web appmobile appmusic streaming catalogplaylist and station features

Pricing model

Freemium and paid subscription models were reported, with monthly unlimited and market-specific paid options. Public sources do not disclose final subscriber economics.

Competitors or alternatives

SpotifyApple MusicGoogle music productsPandoraTidalother licensed streaming services

What happened

Summary

Rdio shut down as a standalone streaming service after Pandora agreed to buy key assets during bankruptcy proceedings.

Outcome

Standalone service shut down; selected technology and intellectual-property assets went to Pandora.

Core risk

In licensed subscription markets, catalog costs and distribution scale can overwhelm a polished product experience.

Shutdown reason

Public reporting points to bankruptcy proceedings and an asset sale. The builder lesson is scale economics in licensed music streaming, not a verified single product-quality defect.

Demand signal

Rdio did not fail because music streaming lacked demand. The risk was that demand in a licensed-content market did not automatically translate into sustainable standalone economics for a smaller service.

Distribution issue

Rdio competed in a category where large platforms had stronger device reach, marketing budgets, catalog leverage, and bundling power. A good interface and broad catalog were not enough to win durable distribution.

Timeline

  • 2015: Rdio promoted international expansion, including an India launch with a large catalog.
  • November 2015: Pandora announced a $75M purchase of key Rdio assets as Rdio sought bankruptcy protection.
  • December 22, 2015: Rdio shut down for users, according to shutdown notices reported by MacRumors.

Before you build

Why it matters

Subscription content businesses can look attractive because revenue repeats, but licensed inventory and acquisition costs may also repeat. Larger platforms can bundle, subsidize, and negotiate from a stronger position.

Primary check

Before building a subscription content product, prove your distribution and cost structure can survive against larger platforms that can bundle, subsidize, or out-license you.

Checklist

  • Run a margin model that includes licensing, infrastructure, support, and acquisition.
  • Pre-sell to one narrow audience before building a broad catalog product.
  • Compare your distribution path against the largest platform in the category.
  • What content or inventory cost grows with usage?
  • Which incumbent can bundle a similar product?
  • What narrow user segment has a non-generic reason to switch?
  • Can your CAC be recovered before churn?
  • Can you win without matching the full incumbent catalog?

Relevant if

  • You are building a subscription media, AI content, or creator-library product.
  • Your product depends on licensed content, paid inventory, or expensive infrastructure.
  • You compete with platforms that already own distribution.

Less relevant if

  • Your product owns unique supply that incumbents cannot license easily.
  • Your market is narrow enough that global platforms ignore it.
  • Your content cost falls as usage grows.

Pre-build tests

  • Launch with one narrow content wedge and measure paid retention.
  • Test whether users still pay when a large incumbent offers a cheaper bundled alternative.
  • Negotiate supply terms before assuming subscription gross margin.

Transferable lessons

  • Model content and acquisition costs before celebrating recurring revenue.
  • Pick a segment where catalog breadth is not the only reason to choose you.
  • Build a wedge around community, workflow, or proprietary supply rather than a generic library.

If you build this today

A smaller team should avoid fighting the full streaming catalog war. Start with a narrow audience, proprietary community or workflow, and a content cost model that improves as usage grows instead of becoming a margin trap.