An Unexpectedly Challenging Start

The development of TuneVote didn’t begin smoothly. From day one, we knew we were stepping into technically demanding territory. Building a truly collaborative music experience required real-time synchronization for multiple users — which meant diving deep into **multiplayer sockets** and handling live updates across devices.

We had to master everything related to real-time communication: managing connections, handling disconnections gracefully, syncing votes instantly, and ensuring the music queue stayed consistent for everyone in the session.

Our First Technical Approach: Spotify Premium API

Early on, we decided on a clear direction for audio playback. After testing different options, one thing became obvious: **Spotify offered the best sound quality**. So our initial plan was to build everything around the Spotify Premium API and Web Playback SDK.

The idea was straightforward on paper:

Use Spotify’s official APIs for searching songs

Stream high-quality audio directly

Build our voting and queue algorithm on top of Spotify’s infrastructure

This approach promised excellent audio fidelity and a familiar music library for users.

The Spotify Premium Hurdle

There was just one big problem: **I didn’t have a Spotify Premium account**.

To move forward, I had to borrow a colleague’s Premium account. With his permission, I created a developer app under his account to access the Spotify API. Then I built a separate test website that could:

Search for songs via a simple input field

Select and play tracks directly in the browser

It took several hours of debugging authentication, handling access tokens, and configuring the Web Playback SDK — but eventually, it worked. I could search for a song, click play, and hear it streaming through the web page.

That small victory felt huge at the time.

The Hidden Downsides (More on This Later)

What we didn’t fully anticipate were the significant limitations and downsides of relying heavily on Spotify’s Premium API for a collaborative tool like TuneVote. These challenges became clearer as development progressed, and we’ll dedicate a future blog post to exploring them in detail.

For now, it’s enough to say that while the sound quality was excellent, the technical and accessibility constraints forced us to think creatively about the long-term architecture.

From Prototype to Vision

That early prototype — a basic web page connected to Spotify via a borrowed Premium account — marked the real technical beginning of TuneVote. It proved we could handle song search and playback, but it also highlighted how much work lay ahead with real-time sockets, group synchronization, and creating a seamless experience that didn’t force Premium requirements on every participant.

This challenging start taught us valuable lessons about balancing technical ambition with user accessibility — principles that continue to guide TuneVote’s development today.

Building the Future of Group Music

Every line of code written during those long debugging sessions brought us closer to a tool that makes collaborative music simple, fair, and enjoyable for everyone — whether at the office, a party, or any shared space.

Ready to experience the result of all that hard work?

**Try TuneVote now** and see how easy it is to let your group vote on music in real time. No complicated setup, and participation is open to everyone.

Create your first session today and turn music selection into a fun, democratic experience.

The Technical Beginning of TuneVote: Tackling Multiplayer Sockets and the Spotify API