Most apps just ask if you liked it.
This one asks which part — the song, the artist, the vibe, or the energy?
Sophisticated algorithms. Billions of data points. And yet they all share the same blind spot: they can't tell the difference between a song that's wrong forever and one that's just wrong right now.
One button cannot tell the difference between a track that's wrong forever and one that's wrong right now. So the system guesses — and your queue slowly drifts away from what you actually want.
The problem isn't that you don't have an opinion. It's that the app can't understand which kind of opinion it is.
Not stronger or weaker versions of the same feeling.
Each one is a fundamentally different kind of intent.
One reaction opens one panel. Every chip is visible. Select what applies, combine freely, tap Done. The algorithm learns. You never leave the music.
Love commits the system — it leans hard into this signal and builds around it. Like keeps things present without obsessing. Both chips add specificity so the algorithm knows what to do more of.
Dislike has more options because there are more ways something can feel wrong. Never keeps it simple — when you're done, you're done.
Chips turn a generic tap into a specific signal. Toggle between states to see exactly how each combination shapes recommendations.
This system can — because every signal tells the system what you mean, not just what you tapped. The quality gap compounds with every tap.
You just watched a problem every streaming service accepts as unsolvable get taken apart and rebuilt around what users actually mean. That's not a concept. That's how MMWB works.
We find the version users didn't know was possible — then make it inevitable.
Your product could work like this.
Tell us what you're building, where the experience is breaking down, or where the idea still feels fuzzy.