Why the Hardest Part of Spotify Mobile Wasn’t the Code
When Spotify launched its desktop app in Sweden in 2008, a mobile version seemed impractical. Phones had limited storage, and dedicated MP3 players dominated. The iPhone changed that calculus, but porting the desktop experience to a device with intermittent connectivity and strict data plans introduced problems the original engineering team never had to consider.
Those constraints shaped three lessons that emerged from developing Spotify's mobile app, as shared in the Spotify: A Product Story podcast series.
Surveys Can't Predict Future Behavior
Even with smartphones available, building a competitive mobile music service faced a fundamental business problem: it couldn't be free. Without a persistent internet connection, ad-supported listening wasn't viable, so the service would need to be paid. Meanwhile, users already had access to free music through piracy.
Spotify settled on a $10-per-month price point after months of licensing negotiations. When the company surveyed users, no one said they would pay that amount. But the team recognized a limitation in their research approach: survey respondents in 2009 couldn't accurately predict how they'd value a product that didn't yet exist.
As Gustav Söderström, Spotify's Chief R&D Officer, put it:
Humans are not very good at predicting our own future behavior, especially when it comes to what we are prepared to pay for something like convenience. We just can't imagine our future selves being that lazy.
User research is useful for understanding current attitudes and behaviors, not for forecasting how people will respond to an unrealized future product. The team had observed that desktop users valued convenience, and believed mobile would deliver substantially more of it. That bet—that people would pay for something they currently got for free if it were significantly more convenient—was the foundation for moving forward.
Desktop Optimization Creates Mobile Blind Spots
Building a mobile experience that could compete with offline MP3 players meant overcoming technical hurdles that didn't exist on desktop. Mattias Arrelid, one of Spotify's early Mac developers, identified two primary challenges.
First, phones lack a constant power supply and high-bandwidth network connection. Spotify's desktop app leveraged peer-to-peer networking, but on mobile that approach would force the device's radio to stay active, draining battery life. Second, mobile data plans were typically limited, so the app needed to be extremely mindful of bandwidth consumption.
The desktop app had been optimized for efficiency—but only as a desktop app. Concerns like power draw and data usage never factored into its design. This optimization bias created blind spots that would have hampered the mobile product if left unaddressed.
The engineering team's solution involved changing the audio codec used to encode music, a decision with technical and business consequences.
Licensing Strategy Matters as Much as Technology
Streaming technology wasn't proprietary to Spotify, and competitors would eventually catch up. The company needed an equally innovative business approach to maintain its edge.
Licensing for music streaming isn't one-size-fits-all. Different use cases—streaming on desktop versus mobile—require different licenses from record labels. Many companies at the time chose to defer that complex work to move faster, but Spotify took the opposite approach, spending months negotiating deals that no other company had secured.
Petra Hansson, Spotify's first general counsel, explained the rationale:
We spent a lot of time getting those licenses right. Because, you know, back in the day, the norm was more to just sign any licenses and then, you know, try and flip the companies, so it became someone else's problem or companies would go belly up. So we were sort of hell-bent. And that's one of the reasons why I joined [Spotify], because what I really liked about the company was that [co-founder and CEO Daniel Ek]'s vision was always to build something long-term and sustainable.
This patience ensured Spotify could launch its paid mobile tier without delays. The lesson: great product development rarely rests on technology alone. Sustained success typically comes from combining technological innovation with business model innovation. In Spotify's case, the codec change enabled technical feasibility, but the carefully negotiated licenses provided the strategic advantage.
