Tuneo

At its core, Tuneo has to be two products at once. One creates music. The other plays it.

The same song needs to work as something you are still shaping and as something a stranger can discover, play, like, and share as a finished piece of content.

People do not arrive with the same creative intent either. One person wants to type a single idea and hear a song seconds later. Another already has the lyrics, knows the genre, and wants control over mood, style, vocals, and every other detail.

Forcing both users through the same creation screen would make the product feel too heavy for one and too limited for the other.

There is also an economy behind every creative action. Each generation costs credits. That means every experiment carries a price, even when the user is simply exploring an idea. The interface needed to make that cost clear without making creativity feel transactional.

What we did

• We introduced the product through outcomes, not forms. Onboarding plays real songs created with Tuneo, so users hear the promise of the product before being asked to do anything.
• We split creation into two distinct paths. A guided flow turns a simple idea into a song through a few lightweight decisions, while the advanced flow gives experienced users direct control over lyrics, genre, mood, style, vocals, and detailed settings.
• We treated every generated song as a real content object, not just an output screen. Each track has artwork, creator identity, play and like counts, lyrics, and actions for downloading, sharing, adding to playlists, or generating another version.
• We let the artwork carry the personality. The interface stays dark and quiet so AI-generated covers become the loudest visual element on the screen. A purple-to-blue gradient is reserved for primary actions.
• We made the credit system feel like part of the product rather than a separate payment layer. Referrals turn invitations into song credits, while the paywall compares weekly and yearly plans openly instead of hiding the trade-off.
• We built the experience as a system from the beginning. Genre chips, track rows, bottom sheets, player states, and creation surfaces all share the same underlying language. That foundation is what later made it possible to package the entire product as a complete UI kit.

“The model makes the song. The product makes it feel like yours.”