Building Sangeet: Why I Created My Own Music Streaming Experience

Most music apps today feel overloaded.

Too many popups. Too many ads. Too many unnecessary features fighting for attention instead of letting users actually enjoy music.

As a full stack developer who’s obsessed with both design and performance, I wanted to build something different.

That’s how Sangeet started.

The Idea

I didn’t want to clone any platform.

The goal was simple:

• Build a modern music experience
• Keep the UI clean and immersive
• Make everything feel fast
• Focus on smooth interactions and aesthetics
• Create something that feels personal

I wanted users to open the app and instantly feel the vibe instead of getting overwhelmed.

The Design Philosophy

A lot of developers underestimate how important motion and spacing are in music apps.

Music is emotional.

So the interface should feel emotional too.

While designing Sangeet, I focused heavily on:

• Smooth transitions
• Soft gradients
• Minimal distractions
• Dynamic player interactions
• Clean typography
• Modern layouts inspired by next-gen UI systems

I spent a huge amount of time refining tiny details like:

• player positioning
• animation timing
• hover feedback
• playlist card spacing
• image scaling
• visual hierarchy

Most users may never consciously notice these things, but they feel them.

That’s what separates a basic UI from a polished experience.

The Tech Stack

I wanted complete control over the app across all platforms. So I built Sangeet using a cross-platform architecture focused on native performance.

Frontend & Framework

• Flutter (for a unified iOS, Android, and Windows codebase)
• Dart
• Dynamic theming & UI powered by palette_generator

Backend & Architecture

• Local Database via Hive
• Background audio service via audio_service
• Native Audio playback via just_audio & media_kit
• State Management via GetX
• Real-time synced lyrics via LRCLIB

Performance was extremely important to me.

Animations are great, but not if they destroy FPS and responsiveness.

So I had to carefully balance visuals with optimization.

Challenges I Faced

Building a music app sounds exciting until you actually start building one.

There were a lot of challenges:

UI Complexity

Music apps have many moving parts:

• playlists
• queues
• player states
• transitions
• dynamic backgrounds
• responsive layouts

Managing all of that while keeping the app visually clean was difficult.

Performance Optimization

Heavy animations can easily make apps laggy.

I had to optimize rendering, reduce unnecessary re-renders, and carefully structure components so the experience stayed smooth.

Creating a Unique Identity

The hardest part wasn’t coding.

It was avoiding making “just another music app”.

I wanted Sangeet to have its own visual identity and atmosphere instead of feeling like a copy of existing platforms.

What I Learned

This project taught me something important:

Good products are not built by stacking features.

They’re built by understanding how users feel while using them.

A fast app is important.

But an app that feels alive is what people remember.

Sangeet helped me improve:

• frontend architecture
• UI/UX thinking
• animation systems
• product design
• performance optimization
• full stack planning

More importantly, it changed how I think as a developer.

I stopped thinking only about “building features” and started thinking about building experiences.

Final Thoughts

Sangeet is still evolving.

There are many features, ideas, and experiments I still want to add.

But this project already represents a huge step in my journey as a developer.

It reflects the kind of products I want to create in the future: fast, immersive, interactive, and visually meaningful.

If you want to check it out:

🌐 sangeet

And if you're a developer reading this: don’t just build projects for the sake of adding them to a portfolio.

Build things that genuinely excite you.

That’s where the best work comes from.