Why RideComposer will never plug into Spotify

It's the first question we get, and it's a fair one:

"Why doesn't it work with Spotify? All my playlists are already in there."

The answer fits in one sentence, and it has nothing to do with willingness or a partnership left to negotiate.

A streaming service never hands over the sound

It hands over playback. An app can ask Spotify to play a track, skip to the next one, stop. That is supported, documented, and plenty of apps do it very well.

But the app never receives the sound itself. The audio signal stays inside a closed box. The app commands the box; it never holds what's inside.

And to do what RideComposer does, you have to hold the sound.

What is impossible without the signal

Four things — and they happen to be exactly what makes a ride a class rather than a sequence of songs:

Beat-matching. Landing the first bar of the next track on the last bar of the previous one means reading both waveforms and aligning them to within a few milliseconds. Without the signal, there is nothing to align.

The tempo curve. Taking a track from 128 to 140 BPM through a climb, without the singer's voice rising with it, is a time-stretch computed on the wave itself. You cannot ask a closed box to slow down a little, just here.

Loops. Replaying the best passage to hold an effort means knowing where it starts and ends, to the sample.

The waveform. Seeing where the strong beats fall means seeing the signal. There is no shortcut.

This isn't a shortcoming of Spotify — it is what a streaming service is. The music is rented there, not handed over.

What streaming-based apps do very well

Fairness matters: they exist, they're useful, and some are excellent at what they do.

They let you structure your class around a playlist, annotate each track with your cues, and show your prompts while you ride. For an instructor who wants to organise a class without touching the music, that's well judged.

What they won't do is mix. Not for lack of skill — because the sound never passes through their hands. When they offer a crossfade, it's Spotify's own crossfade: a setting in the Spotify app, not a transition you built.

Since November 2024, even tempo is closed

Here's something few people know. On 27 November 2024, Spotify closed off audio-analysis data — including tempo — to new applications. Only those with extended access granted before that date still have it.

Put plainly: an app born today could no longer even read a track's BPM through Spotify.

Our constraint became our reason to exist

RideComposer reads the files on your own drive. For a long time this was described to us as a weakness — "you have to own your music."

It is exactly the opposite.

Because we hold the signal, we had to build our own tempo detection. It now reaches 93.6% accuracy on club music — measured, not estimated. We had to write a mix engine, a pitch-preserving time-stretch, waveform reading. None of that could have existed at the end of a pipe.

And there's a last advantage, the kind you measure on a Tuesday evening in a basement studio: your ride plays with no network. No cut-out halfway through a climb, no track vanishing from the catalogue between two classes, no ads.

One question worth asking, whatever the tool

A consumer subscription covers personal listening. Playing music in a paid group class is a different use, with different rights — and that's true with Spotify as much as with your own files. If your club doesn't already handle it, it's worth asking.

It isn't a missing feature

We don't "not have Spotify integration yet." We chose to hold the sound, because it's the only position from which we can do what you ask of us: make the music follow the class, rather than the other way round.

It's the same reason RideComposer still imports MixMeister files, and runs on your drive rather than in a cloud.

Same subject from another angle: why a playlist isn't enough.