Great applications are rarely born in corporate boardroom meetings; they are forged in the fires of late-night coding sessions, driven by a personal need for better tools. Vishesh Gangwar, the lead developer of VxMusic, recounts the roadmap, timeline, and design challenges faced while building a private music player in high school.

The Origin: A High School Project with Big Ambitions

The journey of VxMusic began in late 2023. As a high school student in Class 9, I found myself constantly distracted by the cluttered user interfaces of mainstream music apps. Every popular media player app on my phone was stuffed with features I did not want: podcasts, video feeds, social stories, and endless advertisements. The actual music felt like an afterthought. Furthermore, the memory footprint was absurd, easily consuming 400MB of RAM just to play a simple audio file. I wanted something clean, ultra-responsive, and strictly focused on music. I began drafting plans in my notebook. The core idea was simple: build a lightweight audio wrapper that combines local files with remote library feeds under a beautiful, high-fidelity UI that operates completely client-side without databases or tracking servers.

To achieve this target, I realized that I couldn't rely on pre-made player libraries or templates. Most web-based players relied on standard browser widgets or heavily loaded frameworks. I needed to code the visual layout and the audio routing system from scratch. I spent weeks reading through documentation for Web Audio nodes, CSS flex grids, and standard HTML structures, attempting to understand how to handle large volumes of audio data efficiently.

The Timeline of Development

Building the initial prototype took about six months of self-directed research. I had to learn React, modern state management, and the complexities of the Web Audio API. By 2024 (Class 10), the first operational version was running locally on my laptop. It had a basic glassmorphic panel, simple playlist management, and a canvas-based 2D visualizer.

Releasing V3 in 2026 (Class 11) marked our first public launch. We posted the source on GitHub, shared it on open-source forums, and the feedback was immediate. Users loved the visual aesthetics and the absence of tracking. By mid-2026, we hit 2,000 active users, and in 2026, as I entered Class 12, the downloads crossed the 8.5K milestone. What started as a personal learning experiment had evolved into an active community-driven project.

Managing schoolwork alongside code deployment was an intense balancing act. I would spend my school days learning math and physics, and my nights applying those exact concepts to WebGL shaders and audio signal processing. The pressure was high, but seeing the download count rise and receiving encouraging messages from users around the world made the effort completely worthwhile.

Refactoring for the Open Web

As the user base grew, so did the technical challenges. The initial V1 code was a monolithic mess. State updates for the visualizer were triggering React re-renders for the entire application, causing significant lag on older Android devices. To solve this, we undertook a complete architecture rewrite. We extracted the audio engine into a modular class structure, bypassed the virtual DOM for visualizer ticks, and switched to a local-first state model using IndexedDB. This refactoring reduced the initial load payload to under 1.5MB and brought memory utilization down to a stable 50MB, proving that premium design does not require heavy runtime weight.

We also completely restructured our component directories, creating dedicated folders for shared components and modular hooks. By separating concerns between layout elements, state managers, and raw audio processing nodes, we made the project far easier for external developers to contribute to. The rewrite was painful, but it created the solid foundation that VxMusic needed to support its rapid growth.

Looking Back on the Journey

Building VxMusic taught me more than any textbook could have. It showed me the realities of release lifecycles, user support, and optimization bottlenecks. It proved that a single developer working from their bedroom can build tools that respect human dignity and compete with commercial alternatives. As I look toward future updates, I remain committed to keeping VxMusic open, lightweight, and dedicated to the art of listening.