← All projects
Audio / EntertainmentUX/UI · Development · Brand evolution

Music Player

A mobile music experience connecting discovery, playlists and playback controls through a consistent dark interface.

↓
Music Player — product interface
PRODUCT

Music Player

OUR CONTRIBUTION

UX/UI design
Product development
Evolution of the supplied brand

DELIVERY & CONTINUITY

Publication and release
3–6 months of post-launch support

THE DESIGN CHALLENGE

Keep the current track accessible while giving the library enough room to browse.

The client brought the brand. We developed its expression within the product, designed the experience and built the application. Our engagement continued through publication and a 3–6 month support period, with refinements informed by usage and client feedback. Further support was a separate service.

INSIDE THE EXPERIENCE

Decisions you can see in the product.

01 / DESIGN DECISION

A library with visual anchors

Artwork distinguishes tracks and collections. The home screen groups new releases, popular selections and recently played content into separate browsing contexts.

Music Player — A library with visual anchors
02 / DESIGN DECISION

Playback stays present

The mini-player keeps the current track close to the playlist. A listener can continue browsing without losing the immediate playback context.

Music Player — Playback stays present
03 / DESIGN DECISION

A dedicated listening view

The full player makes the artwork, progress and transport controls the priority. It offers a different level of control without changing the visual language of the collection.

Music Player — A dedicated listening view
EXPERIENCE MAP

The key moments, connected.

A presentation of the interface moments shown in this case.

  1. Browse

  2. Open a playlist

  3. Start playback

  4. Expand the player

Performance model

A closer look at progress.

Different questions deserve different views. Explore the journey, the task and the pattern of return.

01 / TASK COMPARISON

Time to playback

23 sec

-21% vs modeled baseline

Compare the same task across the baseline and iteration.

Modeled baseline29 sec

Time to playback (sec) · zero-based scale

Baseline29 sec
Iteration23 sec
0 sec33.3 sec
02 / COMPLETION MIX

Playback start success

95.1%

+3.9 pp vs modeled baseline

See the completed share alongside the remaining opportunity.

Modeled baseline91.2%
95.1%Modeled completion

Completed95.1%

Not completed4.9%

Baseline → iteration91.2% → 95.1%
03 / ACTIVATION FUNNEL

Collection-to-play

50%

+8 pp vs modeled baseline

Follow the steps between an eligible visit and a completed action.

Modeled baseline42%

Eligible visits → collection-to-play · counts

Eligible visits
1,000
Journey started
720
Key step reached
600
Completed
500
DELIVERED, THEN DEVELOPED FURTHER

A product experience.
Beyond the presentation.

UX, interface design and development came together in a published product. The existing brand was carried into a more developed interface system. Post-launch support provided time for monitoring, client feedback and continued refinement.

Discuss a project ↗
NEXT PROJECT / Marketing / Campaign operations

Orbita CRM

Orbita CRM