AUX.LY

Allowing the audience to control whats played at parties in realtime

Comment

Inspiration

Our inspiration came from always being stuck with one person in charge of the aux at all the group events we went to, so why not let everyone have a say in it?

What it does

Allows for one person to control the speaker still, but the Spotify of the person in control will instead follow a crowd-controlled queue that is built by the people

How we built it

Using ASP.NET Core and SignalR for the realtime communication and backend with React and React Native for both frontends

Challenges we ran into

Syncing all the projects and also syncing both the React Native and React projects to look similar and also act the same. They also had to all call the same endpoints with the same types even though they were in different projects.

Accomplishments that we're proud of

The real-time aspect of the app, with it updating in front of the user with the changes made, whether that be the pause and play of the ap,p or what is currently playing and what is going to be played next.

What we learned

The challenges and applications of real-time communication through Websockets and general RPC, and also learning React and React Native, while also juggling the challenges of OAuth 2.0 with Spotify. Keeping the devices in sync was a very difficult yet rewarding process that exposed us to the real-world complexities of real-time programs.

What's next for AUX.LY

Widespread adoption (hopefully), and optimizing to scale with many users being able to make realtime requests and see these realtime results. Also maybe expanding to other types of entertainments such as media and books.

Share this project:

Updates