Rebuilt Myanmar's well-known music streaming app around a single player — five content types, shipped live in stages across two years.
What's Melo Music?
Melo is Myanmar's one of the music streaming services — and "streaming service" undersells it. It streams, but it also sells: subscriptions by the week or the year, albums bought outright, songs turned into ring-back tones, karaoke, live performances.
That spread is arithmetic, not ambition. Subscriptions alone don't carry a market where most people don't hold a payment card. So Melo takes money seven ways and gives people more than one thing to spend it on. Five content lines, one app, almost entirely Android.

A revamp that wasn't a revamp

One Player, Five Modes
The old player carried five icons under the transport controls, including Ringtune — a paid product — as an unlabelled phone glyph, and a pill reading "lyrics not available" in the most visible slot. The row was also full, with karaoke, live and podcast still to come.
I replaced the icons with a labelled rail: Ringtune, Lyrics, Karaoke, Comment. Playback stays identical across every content type, so a new mode means a new chip rather than a new player. Alongside it, the background now draws from the cover art, the title sits left with like and overflow beside it, and the audio quality badge moved onto the progress bar.
The trade-off is visibility. The rail scrolls, so the fourth chip falls off-screen on smaller devices — karaoke sits at that edge. A fixed row showed everything at once; I chose a system that could grow.


One Library, Not Two


Store For Music Lovers

Live & Videos

The System Underneath
Melo had no design system. Five content types, two years of staged releases, and no shared definition of a button, a row, or a sheet — every feature was drawn from scratch and matched by eye. I started with semantic tokens: colour, type, icon and spacing named by purpose rather than value, so changing one intent couldn't leak into another. Type was the hardest foundation, since Burmese and Latin had to share a single scale without either breaking, and that set the line heights everything else was measured against. [Contrast against album-art backgrounds.]


Components and handoff




Reflection
Designed and shipped in stages throughout 2023-2025. There are a few things that I'd change is all downstream of the design.
Tokens that reach the code: Mine lived in Figma and got re-entered by hand.
Motion in the system: I specified states and spacing, not transitions — so movement got decided in build.
Accessibility in the foundations: Contrast was covered. Colour-blind safety, targets and screen readers weren't.
A feedback loop: Two years of releases and no channel to hear from users.



