The short version
Setlst came from noticing how much live performance planning still happens across notes apps, screenshots, text threads, and memory.
The idea is a cleaner home for the practical details around a set: what songs are being played, where the event is, what needs to be ready, and what changed since the last show.
The problem
Performers and small teams often have the information they need, but it is scattered across too many places.
The goal was to make the workflow feel lightweight enough to use before a show, while still structured enough that important details do not get lost.
What I built
- setlist organization flow
- event and show detail structure
- dashboard concept for upcoming performances
- song and note management patterns
- early product interface direction
Design decisions
The interface needed to feel fast and calm. A music tool like this cannot feel like admin software first; it has to respect that the user is trying to get ready to perform.
I focused the concept around the next show, then let deeper song and planning details sit one level below that.
Technical decisions
The project is structured as a product prototype first, with the data model shaped around shows, songs, notes, and reusable setlist details.
Challenges
The main challenge is keeping the product simple. It is easy for a setlist app to become a full project-management tool, but the useful version needs to stay close to the moment of performance.
The outcome
Setlst is a strong example of how I think about workflow products: take a messy real-world process, identify the repeated decisions, and give them a calmer interface.
What I'd improve next
The next step would be tightening the core show-planning flow and adding real screenshots once the prototype is more visually complete.