Tuneo

The Tuneo experience covered two connected flows: generating music with AI and listening to or sharing the result. The same track had to work as a draft during creation and as discoverable media after publishing.

Users also arrived with different levels of input. Some wanted to begin with a short idea, while others expected detailed control over lyrics, genre, mood, and vocals.

A single long form would add unnecessary effort for the first group and provide too little control for the second. The information architecture needed to support both intents within one system.

Each generation also used credits. Cost had to appear at the point of decision without turning every creative step into a payment interruption.

The work began as a freelance product design project. It was later expanded into a reusable UI kit for a broader range of music products.

Design approach

• 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.

Outcome: creation, playback, sharing, and the credit model were defined as one end-to-end component system, which later supported the UI kit release.