Launched this week
MUSIXQUARE
Turn any room into a surround system with your devices
81 followers
Turn any room into a surround system with your devices
81 followers
Got multiple phones or tablets lying around? MUSIXQUARE turns them into a synchronized surround sound system. Right in the browser, no install needed. Assign each device a role (Left, Right, Center, Subwoofer) and play the same track perfectly in sync across all of them. Share local files, YouTube videos, or even your system audio with everyone in the room. More Devices, Richer Sound. Free to start! Works on any device with a modern browser. Try it at musixquare.com
MUSIXQUARE
Hello Product Hunt!
I'm a 4th year architectural engineering student. Acoustics is part of my major, and I've always been fascinated by how sound shapes a space.
MUSIXQUARE started mundanely. I was watching a movie with friends on a laptop with terrible speakers. We had three phones sitting on the table, and I wondered why can't these just work together as speakers? No Bluetooth pairing, no expensive gear, just a webpage.
So I built it. Open musixquare.com on any device, assign it a role (Left, Right, Center, Subwoofer), and play the same track in perfect sync. Works with local files, YouTube, and system audio. No install and free.
Honestly this project humbled me. I want to be upfront about three walls I couldn't break through, despite months of trying
1. YouTube doesn't support channel separation.
The IFrame API doesn't expose raw audio (CORS + DRM restrictions), so Left/Right/Center routing only works with local files. YouTube plays as a full stereo stream on every device.
2. System audio sharing is desktop-only.
Mobile browsers (iOS Safari, Android Chrome) don't expose `getDisplayMedia({ audio: true })`. Apple and Google simply haven't shipped it, and there's no polyfill possible. If anyone here has ideas, I'd genuinely love to hear them.
Everything else(device sync over flaky Wi-Fi, role-based positioning for local files, YouTube co-watching, real-time chat, even a system-audio broadcast mode for desktop) took months of rewriting the architecture from scratch. I'm genuinely proud of where it landed, even with the gaps.
Would love your feedback, especially from audio/web folks who can point out what I'm missing. What would make this actually useful for your setup?
I really appreciate you for checking it out!!
Really clever use of the browser as a multi-device coordinator — the zero-install angle matters a lot for casual setups where you don't want to commit to an app ecosystem.
From a content creator angle: I run the ModeLoop Podcast (https://open.spotify.com/show/0m1oR8AyQv17DVpc5MmirG) covering financial modeling and M&A, and one thing I've never been able to justify is a dedicated speaker setup just for monitoring playback across devices. The idea of repurposing phones/tablets as surround nodes for listening back to edited audio is genuinely useful — you want to know how an episode sounds on different devices before publishing, and this could make that workflow a lot lighter.
Does it handle mono/stereo podcast audio cleanly, or is the experience optimized primarily for music with full surround encoding?
MUSIXQUARE
@samir_asadov Thanks for thinking this through so carefully. The podcast monitoring use case is a strong fit even though I hadn't optimized the language around it. and my Quick answer is: yes, both mono and stereo play cleanly.
Stereo podcast: Channel routing works as expected. Assign Leftto one device, Right to another, and you get true stereo separation. Useful for catching panning issues or balance drift mid-episode.
Mono podcast: All assigned devices play the same signal in unison. The L/R/Center/Sub roles still work, they just act as duplicates rather than splitting channels. Still useful: place phones at listener-typical positions (desk, couch, kitchen counter) and hear how the mono mix translates across spaces simultaneously.
The product labels assume a music multichannel layout (L/R/C/Sub), but mechanically the graph routes per-device on whatever audio you throw at it. Would love to know if you actually try it, and what falls short for podcast specifically. Genuinely curious what a financial-modeling podcaster wants from a listening tool.
Thank you.
@hiefny That's a really strong use case — podcast monitoring could be a whole vertical on its own. Would be worth surfacing it more prominently in your positioning. What would it take to make MUSIXQUARE the go-to tool for podcast analytics?
MUSIXQUARE
@samir_asadov Honestly, the positioning note is well-taken. I've been thinking about it in music terms and the podcast monitoring angle didn't make it into the copy. Worth fixing.
honestly, MUSIXQUARE is the synchronized playback layer, not the analytics layer. What I could see working is using it to audition your episode across real devices simultaneously, then bring your own notes. The gap between that and actual analytics is probably a dedicated session log or shareable timestamp markers. it isn't impossible, but a different scope than what exists today in MXQR. (Actually, there's already a playback timestamp on every chat message, one small step from there to clickable seek markers. That could make the annotation workflow a lot lighter) I could add something into roadmap.
If you try the monitoring workflow before a publish, I'd genuinely want to hear what's clunky. Comments like yours are exactly what turn a half-formed idea into something real. thank you for that.
Love it! Does it works with streaming services like Apple Music or Spotify?
MUSIXQUARE
@deeb99 Thanks Rosario!
I really wanted to support them, but Spotify and Apple Music don't allow third-party apps to access the audio stream (DRM/licensing), which makes synced playback impossible from the outside. Wrote up the full reasoning under "Not ours to fix" on the roadmap: musixquare.com/roadmap
Additionally, MUSIXQUARE on Windows/Mac chrome, there's a system audio sharing mode that captures anything playing on your machine (Spotify, Apple Music, Netflix…) and streams it synced to every other device. The host just has to mute their own output because of the latency cannot be controlled.
Appreciate you stopping by!
MUSIXQUARE
Hello Product Hunt! We're officially live today.
Three pages for anyone curious about the deeper layers:
• Roadmap → musixquare.com/roadmap (every known limit, sorted into Now / Next / Not ours to fix)
• Changelog → musixquare.com/changelog (the path from Aug 2025 to today)
• Design system → musixquare.com/designsystem
Huge thanks to everyone who's been around since the upcoming page. It means a lot
===
Update: a TURN endpoint gate from a recent security pass was returning 403 to same-origin requests without an explicit Origin header, breaking cross-network rooms for the first ~10 hours of launch.🤦♂️ Fixed and deployed. If you tried it earlier and the join failed, please give it another shot.