Spotify launched two new features on July 30, 2026: User Notes, which lets listeners attach personal text annotations to individual tracks within playlists, and Running Mode, a premium-only feature that sequences music according to run phases and user preferences (TechCrunch).

User Notes is available to Spotify users aged 16 and older on both free and premium plans in select markets. The feature lives inside the playlist context: a user navigates to a playlist, taps the three-dot menu next to a song, and selects "Add note." The resulting annotation is visible to anyone who can see the playlist, with the note creator's name linking back to their Spotify profile (TechCrunch).

Running Mode, launched the same day, is narrower in availability. It is restricted to Spotify premium subscribers in select countries. Rather than functioning as a simple shuffle or playback queue, Running Mode cues up songs based on run phases and user preferences, suggesting a context-aware sequencing model tied to the physical cadence of a workout (TechCrunch).

Both features were reported by TechCrunch based on a statement Spotify provided via email. There is no publicly linked Spotify announcement page corresponding to the launch as of the report's publication, which means the details come through a single media intermediary rather than a primary product page or blog post that readers can verify directly (TechCrunch).

The visibility model for User Notes is worth examining. Because a note is tied to the playlist's share scope rather than to a private user space, the feature effectively turns collaborative and public playlists into annotated objects. A note written by one user becomes part of the experience for everyone with playlist access. The creator's name linking to their profile adds an attribution layer that sits somewhere between a social tag and a byline. This raises a straightforward product question: what moderation, reporting, or abuse-prevention infrastructure surrounds user-generated text attached to shareable playlists? The available facts do not address this, and the absence of a public announcement page makes it harder to cross-reference any related policy documentation.

The 16-and-over age gate is the only explicit access restriction mentioned for User Notes. Running Mode, by contrast, carries both a premium-tier requirement and a country-level limitation, which is a tighter distribution pattern and more typical of features involving additional licensing, infrastructure, or partner agreements. Without Spotify's primary documentation, the specific countries included in either feature's rollout are not identified in the reported facts.

Looking at what this means for Spotify's product direction, User Notes and Running Mode sit at different points on the spectrum between social engagement and contextual personalization. User Notes adds a user-generated content layer to a music platform whose social features have historically been lightweight and somewhat transient. Spotify has cycled through social experiments before, and the durability of a notes feature depends heavily on whether users treat playlist annotations as worth the friction of creating them. The three-dot-menu access path is low-friction by design, but adoption will depend on whether the social context in which a playlist is shared actually rewards annotation.

Running Mode is more structurally interesting from a product engineering standpoint. Phase-based cueing implies either a predefined tempo or intensity map matched to typical run structures (warm-up, steady-state, intervals, cooldown), or a dynamic model that adapts to live biometric or accelerometer input. The facts available do not specify which, and that distinction matters: a static sequencing model is a curated playlist with metadata; a dynamic one that adjusts to real-time pace is a meaningfully different technical proposition. The premium-only gating is consistent with either approach, but a dynamic model would more clearly justify the subscription requirement through the compute and sensor-integration overhead involved.

Both features are launching in select markets with no publicly available primary documentation. For developers, partners, or observers trying to assess the technical architecture or API implications, that is a notable gap. Spotify's email-based communication to TechCrunch confirms the launch and its core parameters but leaves the implementation details, rollout roadmap, and supporting policy framework unaddressed in the public record.