Version 1 of this player, and to be honest, my first player design. How could I improve it?

#buildinpublic #dataviz #music

How would you do it differently? 🤔

#buildinpublic #uidesign

Filtering logic and UX was a little challenging because there's like 2,500 genres.

To simplify, I grouped sub-genres under their parent genre, while still allowing the parent to be selected on its own

Slightly unconventional, but avoids clutter from duplicate parent checkboxes

The genre relationship data is all from MusicBrainz at the moment. UI made with React, Motion, and Shadcn

#buildinpublic #uidesign #dataviz

Next up is setting up some clustering logic. Some I've been thinking about are clustering based on shared artists, cultural proximity (time and place), popularity (cumulative listeners and number of artists), and genre hierarchy.

What other ways of clustering could be useful for discovery?

Very cool! Can I ask what tool you’re using for these for graph visualizations? I’m working on an app right now that lets users explore music data spatially using react-force-graph

Looking into using the url-rels endpoint from MusicBrainz so we’ll see how that goes. Will definitely check out Deezer. Thanks for tips 🙌

What were the apps? Curious to see what you could produce in two days :)

One thing I’m a bit concerned about is walk-up observers not getting the full context of our conversation — which could mean we either miss the chance to gather feedback from them entirely, or we end up getting feedback that isn’t accurate.

I'll be gathering feedback on a new enterprise application feature in a busy expo-style booth.

Has anyone run quick discovery or usability sessions in a customer-facing conference setting? What formats or tactics helped you collect honest, actionable insights in just a few minutes per person?