Why doesn't your music history show what your year was actually like?

Every year-end music recap works the same way: it counts. Most-played song, most-played artist, total minutes, all sorted by frequency. So the recap arrives, and it is oddly deflating — the top song is one you do not remember choosing, attached to no memory in particular, while the song that was actually playing during the one afternoon you would call the center of your year does not even make the list. The recap is not wrong. It is just measuring something else.

A play count and a meaningful year are different measurements

Streaming history is built to answer "what did you play the most," which is a question about repetition, not about significance. A song can top your year by being looped for three straight weeks while you worked through something you barely thought about consciously, or by being a toddler's one demand on every car ride, or by being whatever the app queued next while you were not paying attention. None of that requires the song to have mattered. Meanwhile the song playing at the one dinner, the one drive, the one night that actually shaped how the year felt might have played exactly once — a single data point, invisible to a ranking built on volume.

The recap has no memory of why

Even where the two do line up — a song you played constantly because it mattered — the recap still cannot tell you why. It knows the count, not the reason. A year from now, the ranked list will still say the number, but you will have already started forgetting what was happening when the song became the one you needed on repeat. The context that made the frequency meaningful was never captured anywhere; only the frequency was.

It was built without you noticing, which is also its limit

Part of what makes a listening recap feel almost magical is that you did not have to do anything for it — it assembled itself in the background while you lived your year. That is a real convenience, and also exactly why it cannot tell you what your year was about. Anything collected without your attention reflects what an algorithm served you, not what you noticed, chose, or thought was worth remembering. A record with any of that in it has to include a moment where you, not the software, decided something was worth marking down.

What a one-line record catches that a play count cannot

None of this means the recap is a bad idea — it is a pleasant piece of trivia about your year, and a genuinely fun one. It just is not a record of your year, because it was never built to notice what you noticed. A different kind of record — a line you write yourself, on the day, about what you were doing — starts from the opposite end: it only exists because you thought it was worth a sentence, so its bias runs toward meaning instead of repetition. It will just as easily hold the single afternoon that never repeated as it holds the ordinary week that did.

TimeMap keeps that second kind of record. A line about what you were doing, given a colour, saved with its date — no play count, no ranking, no algorithm deciding on your behalf what counted. Look back later and you get a calendar of it, a summary of the words you used most, two stretches of time set side by side, or a sphere of your own tags to wander through. None of it is sorted by how often something happened. It is sorted by what you actually thought was worth writing down.

A recap will always be able to tell you what played the most. Only a record you kept yourself can tell you what the year was actually like.