System model
The app owns the room. YouTube Music feeds the queue.
Mutive is designed around channel state, permissions, chat, and queue logic. V1 now assumes a single YouTube Music-centered search and playback surface.
Why it feels different
The product is closer to a control room than a landing page.
Everything on screen should help someone operate, observe, or join a live listening session.
Real-time synchronization is the center of gravity. Viewers are supposed to understand instantly what is playing, who can act, and what the room is doing.
That is why the interface now favors dense status surfaces, queue readability, access states, and room activity over marketing sections or decorative explanation blocks.
The current implementation is still a prototype, but the visual system now matches the intended product behavior much more closely.