~/projects/flowlistJesse Zeng / portfolio
All projects

FlowList

Role
Independent project
When
2026 / ongoing
Stack
Next.js / TypeScript / Tailwind
Status
Product prototype

Why I built it

A playlist is a collection, but listening happens in an order. I wanted to give people a way to shape the movement between tracks without replacing the music they already chose.

Who it is for

The tool proposes a sequence that the listener can inspect and revise. The purpose is creative control: make the transition from a pile of tracks to an intentional listening session easier.

My contribution

I built strategy-based sequencing, transition scoring and an editable result workflow. The newer code supports endpoint locks, manual reordering and comparison with the original order, alongside platform integration work.

Sequencing

The sequence starts with chapter structure, then scores positional fit and neighbouring transitions before bounded local refinement. Duplicate occurrences and strategy constraints are preserved.

  1. StructureChapters / endpoints
  2. ScorePosition / neighbouring tracks
  3. RefineBounded search / preserved constraints
Mood and rhythm are metadata-based estimates, not audio measurements. The result is a proposal for the listener to judge; it is not a claim of a globally optimal or objectively better musical order.

Listener control

A listener can adjust an estimated order rather than accept it unchanged. After edits, transition explanations are recalculated so the interface reflects the current sequence.

Interface

FlowList demo with a ten-track sequence, chapter labels and estimated energy and rhythm.
Public demo captured October 3, 2026 / fictional tracks / estimated features.

Where it stands

The public demo runs through to a result with fictional tracks. The local editor and export work is newer than that deployment; account integrations and listening quality remain areas for further validation.