← Back to the timeline

2025 / FIRST SYSTEM I SHIPPED END-TO-END

Tunesta.

What happens when your music library has to hold songs no streaming service has?

A personal music library for uploading and playing original recordings, built for my brother.

STATUS & SCOPE

Personal project · full-stack application

TECHNOLOGIES

Node.js · Express · MongoDB · React

THE USEFUL OUTCOME

What this makes possible.

A dedicated place to upload, organise, and play personal recordings outside a streaming catalogue.

THE ENGINEERING SIGNAL

What the work demonstrates.

Separated audio storage from database metadata and connected the full upload-to-playback flow.

01

Why I Built It

My brother records his own songs and needed a personal library for music outside streaming catalogues. I built a dedicated place for his recordings.

02

The Problem

I needed a place to upload, store, and stream audio files without depending on a platform's personal-library rules or licensing assumptions.

03

The Decision

I stored audio files in Cloudinary and kept their metadata in MongoDB. My backend connects uploads, retrieval, and playback without storing large audio files in the database.

04

What Changed

This was my first experience owning the complete flow from upload to playback. It taught me how frontend interactions, backend routes, file storage, and database records fit together.

05

What I Could Add In The Future?

Improve song search and review security and scaling before expanding to shared listening rooms.

HAVE A RELATED CHALLENGE?

Let’s talk about your project.

NEXT PROJECTCoreWire →