Live web experience · iOS beta

OmniPlay.

Share the song,
not the service.

One neutral music link for Spotify and Apple Music, designed across a native iOS app, Share Extension, and responsive web experience.

A project by
Casey Childs
The work
Product strategy · Product design · iOS · Web
OmniPlay's dark web interface with the statement One link. More music. and a search field.
OmniPlay / Live web experienceWeb

The song was right.
The link was wrong.

Sharing music still asks the sender to guess which service the other person uses. A Spotify link is friction for an Apple Music listener, and the moment can disappear inside a service decision.

OmniPlay reframes the link as a neutral handoff. The sender shares the music once. The recipient chooses where to listen, without needing to install an app.

The product principle

The sender should not have to choose the recipient’s music service.

Find it once.
Open it anywhere.

OmniPlay connects two deliberately small experiences. On the sending side, search for a song, paste an existing link, or use the iOS Share Extension. On the receiving side, one responsive page offers the available services and remembers the listener’s preference.

Matching uses catalog identifiers and careful fallbacks. Preview playback appears when the Apple Music catalog provides it, keeping the result useful without pretending every track has a universal preview.

  1. 01Find or share

    Search, paste a link, or send from another app.

  2. 02Make one link

    OmniPlay resolves the music across supported services.

  3. 03Choose and listen

    The recipient opens Spotify or Apple Music.

OmniPlay displaying a resolved track with album artwork, Preview, Copy Link, and Share controls.
A resolved song / Ready to preview and shareLive web

Built into the way
music gets shared.

The iOS beta brings OmniPlay closer to the moment of intent: search or paste inside the app, share from Spotify or Apple Music through the extension, recognize a song with Shazam, and keep a local history of links sent and received.

The interface stays native and restrained. Sharing, copying, previews, and system materials do the work; OmniPlay adds only the context needed to move the song forward.

OmniPlay on iPhone showing first-share onboarding over the app's home screen.
First-share onboarding / Current iterationLocal build

Meet people where they share.

The Share Extension turns an existing service link into an OmniPlay link without making the sender restart the task.

Keep history private by default.

Shared and received links are stored locally. OmniPlay does not need a social graph or account system to be useful.

Use the system, quietly.

Native sharing, preview behavior, and song recognition keep the app capable without turning it into another music destination.

No app required.

The shared link opens into a focused choice instead of a marketing page. The artwork confirms the music, the service buttons make the next step obvious, and a small escape hatch lets the listener change a remembered preference.

That web fallback is the product’s connective tissue: a useful endpoint for anyone, whether or not they have the iOS app.

OmniPlay recipient page offering Spotify and Apple Music choices for a song.
Choose a serviceDesktop web
OmniPlay's recipient service choice on a mobile screen.
The same handoffMobile web

LIVE TODAY

A small product,
working end to end.

OmniPlay is live on the web and available as a public iOS beta. The current product resolves tracks and albums between Spotify and Apple Music, supports native and web sharing, and keeps analytics deliberately limited to product events rather than music or identity data.

The next work is refinement: strengthening matching, learning from the beta, and deciding which additions earn their way into an intentionally focused product.

Open original image