DEV Community

april cc
april cc

Posted on • Originally published at webharmonium.space

I Built a Browser-Based Harmonium for Practice, Learning, and Play

When people think about music software, they usually think about DAWs, plugins, piano apps, or guitar tools.

Very few people think about the harmonium.

That felt strange to me, because the harmonium is still one of the most recognizable and widely used instruments in Indian music, devotional music, vocal accompaniment, and music learning. It sits at an interesting intersection between Indian classical music, Western note systems, and accessible keyboard-based playing.

So I built Web Harmonium — a browser-based harmonium that lets you play instantly online with keyboard, touch, or MIDI, with no installation required.

Why I built it

I wanted something simple:

  • open a webpage
  • press a key
  • hear a harmonium note instantly
  • practice melodies or note patterns without friction

A physical harmonium is great, but it is not always nearby.
A desktop app adds installation friction.
A generic keyboard app does not really capture the learning context of the harmonium.

I wanted a tool that felt more like:

  • a lightweight practice instrument
  • a note-learning tool
  • a bridge between Sargam and Western notes
  • something musicians and learners could access from anywhere

What the product does

Web Harmonium is designed to be playable right away.

It currently supports:

  • Keyboard input for quick desktop play
  • Touch input for mobile and tablet use
  • MIDI controller support for people who want a more physical playing experience
  • Sargam + Western note labels on the keys
  • Transpose controls
  • Reverb and reed settings
  • Basic raga-oriented learning context

The main idea is not to perfectly simulate every physical nuance of a traditional harmonium.
The goal is to make the instrument more accessible on the web for:

  • quick practice
  • melody exploration
  • beginner learning
  • experimenting with note relationships

The design challenge

Building something like this is not just about playing audio files.

There were a few important constraints:

1. It had to be instant

If a user opens a music tool and has to sign up, install something, or wait through a clunky setup flow, most of the magic is gone.

So the product had to feel like this:

open → press → play

2. It had to work across devices

A lot of browser tools work well only on desktop.
But for a musical tool, mobile matters too.

That meant thinking carefully about:

  • touch interactions
  • layout scaling
  • key sizing
  • keeping the interface playable rather than just visually responsive

3. It had to feel educational, not just decorative

A browser instrument is interesting for a few seconds.
A browser instrument with a clear learning angle is much more useful.

That is why I leaned into:

  • note visibility
  • Sargam and Western notation together
  • practice-oriented interaction
  • basic raga exploration

What I learned from building it

1. Niche products can be clearer than broad ones

A broad “online music app” would be hard to position.
A browser-based harmonium is much more specific.

That specificity helps with:

  • product messaging
  • user understanding
  • community sharing
  • SEO direction

2. Web-based tools are underrated when they remove friction

A lot of people still underestimate how powerful simple browser tools can be.

If the product solves a narrow problem quickly, the browser is often the best place for it.

No install.
No setup.
No commitment.

That is a huge advantage.

3. Educational utility makes tools more durable

If a product is only “fun,” it may get shared once and forgotten.
If it is useful for learning, it has a much better chance of becoming part of someone’s routine.

For this project, that means the long-term opportunity is not just “play harmonium online.”
It is also:

  • learn notes
  • understand Sargam
  • practice ragas
  • explore melody ideas

Challenges after launch

Launching the product is only the beginning.

The biggest early challenge is not development anymore.
It is distribution.

This kind of project does not fit neatly into the usual categories:

  • it is not a generic AI tool
  • it is not a mainstream SaaS product
  • it is not only for developers
  • it is not only for professional musicians

So the go-to-market path is more community-driven:

  • music communities
  • Indian classical music learners
  • browser tool directories
  • side project communities
  • product showcases

That has been a good reminder that for niche products, distribution strategy has to match the audience very closely.

Who this is for

Right now, I think Web Harmonium is most useful for:

  • harmonium learners
  • Indian classical music students
  • vocalists who want quick reference notes
  • musicians experimenting with melodies
  • anyone curious about browser-based instruments

What I want to improve next

There are a lot of directions this could go:

  • better educational modes
  • more guided raga practice
  • richer tonal customization
  • improved onboarding for first-time users
  • better MIDI workflows
  • sharable exercises or note patterns

I am especially interested in improving the product in ways that make it more useful for actual learning, not just casual novelty.

Try it

If you want to try it, here it is:

https://www.webharmonium.space/

If you build unusual browser tools, music products, or niche learning products, I would love to hear how you think about:

  • reducing friction
  • making tools feel instantly useful
  • balancing simplicity with depth

If you have feedback, I would genuinely love to hear it.

Top comments (0)