Why Spotify’s Client Platform Team Invested in Apple Silicon

Spotify’s Client Platform (CliP) team exists to unblock client developers and maintain a high-quality developer experience (DX). When the company’s quarterly Engineering Satisfaction surveys flagged long build times as a recurring pain point, the team set out to address the problem at the infrastructure level rather than only optimising code.

Early experiments showed that moving development work to Apple silicon machines could cut iOS build times by 20–30%, with reductions up to 50% on the newest M1 Pro and M1 Max chips. That prompted a formal effort in 2022 to validate both the performance and the business case for a hardware refresh.

Defining the Problem and Success Criteria

The project had two central questions:

  • Were current machines good enough for Spotify’s client developers?
  • Would the performance gains justify the capital outlay?

For this analysis, “good enough” was defined as a statistically significant improvement in local Android and iOS build times. The team’s hypothesis was simple: AvgLocalBuildTime(M1) < AvgLocalBuildTime(non-M1).

The inspiration for extending the evaluation beyond raw performance came from a Reddit engineering post on mobile developer productivity, which argued for validating the financial return of hardware upgrades, not just the technical merits.

Empirical Performance Results

Testing across real build workloads produced clear results:

  • Overall: Apple silicon machines were about 43% faster than Intel-based Macs.
  • Android builds: approximately 50% faster.
  • iOS builds: approximately 40% faster.

The financial analysis was equally favourable. The upgrade was projected to break even in roughly three months, with potential savings of up to 36% in engineering costs per team. These findings satisfied both criteria, confirming that the upfront investment was justified.

Prioritising Upgrades Across a Distributed Workforce

Rolling out the new hardware required updating Spotify’s development infrastructure to support the new architecture. A dedicated workstream assisted developers during the transition, and teams across the organisation were asked to ensure their dependencies and tooling were compatible.

Since the new machines had proven superior, the CliP team recommended an expedited upgrade outside the normal replacement cycle. That raised two practical questions: who gets the machines first, and how do you manage logistics when developers are spread across the globe?

Prioritisation was handled in two tracks:

  • New joiners: Tech Procurement updated the standard hardware catalogue so new developers started with Apple silicon from day one.
  • Current employees: upgrades targeted older models and machines with lower RAM, as those factors had the most significant impact on developer experience.

The physical rollout was a substantial operation. It involved shipping machines to hundreds of engineers in 11 countries through five different suppliers. Keyboard language preferences meant five distinct SKUs, each subject to its own supply chain constraints. The team worked directly with resellers and OEMs to minimise delays and get the hardware into developers’ hands as quickly as possible.

A key part of the process was sustainability. Spotify’s distributed-first model and carbon-reduction commitment meant recycling old machines rather than discarding them, so the team coordinated the collection and proper disposal of retired hardware with Tech Procurement.

Developer Feedback Six Months Later

To measure the real-world impact, the team surveyed 100 client developers who had received the upgrade. Working with internal user research experts, the survey focused on three pillars: development experience, productivity perception, and task success.

  • Development experience: roughly 98.8% of respondents rated their experience 4 or 5 out of 5.
  • Productivity perception: about 91.6% rated their productivity 4 or 5.
  • Task success: approximately 83% reported a positive change in task completion, rating it 4 or 5.

Free-text responses reinforced the quantitative results, with developers highlighting faster builds and less wait time as the most noticeable improvements.

Lessons on Communication and Flexibility

The rollout was not without friction. Vendor lead times were unpredictable and shifted estimated delivery dates multiple times. The team mitigated this by maintaining a transparent information flow, updating developers immediately when new details emerged, and answering questions quickly. That steady communication helped maintain trust and patience even when deliveries were delayed.

The experience also reinforced a broader principle: standard practices sometimes need to be set aside to support employees effectively. By prioritising the developer experience through an early hardware upgrade, the CliP team has taken a concrete step toward its goal of keeping Spotify’s client engineers satisfied and productive.