fizy, Turkcell, 2019 to 2021

Rebuilding fizy around how people listen

The app looked the same on every visit, search needed the exact song name and screens followed no shared rules. I rebuilt its core around how people actually listen: discovering, picking a mood, finding a song and making the app feel like their own.

Role
Senior Product Designer
Team
Two product designers, a design manager and the fizy product team
Timeline
Aug 2019 to Nov 2021
Scope
Mobile app and web
Redesigned fizy app screens: mood picker, podcast, discovery homepage, artist page and onboarding
My role
Designed roadmap work from brief to release across the mobile app, the web player and fizy.com, and started the design system behind them.
Problem
Listeners found the app repetitive and hard to navigate, and with no shared system every change was slow.
Impact
One design language for 1M+ monthly users, on one font family and one design system.

Overview

fizy is Turkcell’s music, podcast and video service, with more than a million monthly listeners. The mobile app was the main product. For two years I designed across the app, the web player and fizy.com, from brief to release.

fizy mood and genre covers: summer, sleep, party, oldies, metal, jazz, rock and more

Problem

One look on every visit

The homepage showed the same content every day and hid genres at the bottom. Listeners had few ways into new music, even though moods were one of the most loved features.

→ Shapes Decisions 01, 04 and 07

Hard to find your way around

In tests people completed their tasks, but got stuck on discovery, settings and My Music. Playlist actions were scattered across the page with no clear order.

→ Shapes Decisions 02

Search that needed the exact title

Search only worked with the exact song name, so many people looked the title up on YouTube first and then came back to fizy to play it.

→ Shapes Decisions 03

No system behind the screens

There was no design system and no file of the live flows. Every team rebuilt the same parts, and the web player fell behind the mobile app.

→ Shapes Decisions 06

Outcome

Everything shipped, to 1M+ listeners

Monthly listeners

1M+

on one design language

Themes shipped

14

on deadline, all on one color logic

Platforms

2

mobile and web, on one system

Approach and rationale

What the research showed

An external research lab ran the customer experience and market research. The product team turned it into five goals, and I used it, together with design benchmarks and desk research, to shape each decision below.

  • Finding 01

    Mood is how people listen

    Music helps people live a mood or move into one, and mood was one of the most loved features.

    → Drove Decisions 01
  • Finding 02

    People search by lyrics, not titles

    Search failed without the exact song name, so many found the title on YouTube first.

    → Drove Decisions 03
  • Finding 03

    People want an app that knows them

    They asked for a plainer interface that knew their taste, and got stuck on settings and My Music.

    → Drove Decisions 02 and 04
  • Finding 04

    Listeners felt close to fizy

    They wanted it to keep its familiar side and still feel fresher and more colourful.

    → Drove Decisions 04

Execution

Changing how the team worked

I was a consultant, first through IBM iX and then Amaris. I managed no one, and still changed how a client’s product team worked.

Proposed the design system

It started as my idea, not a request. The product team backed it, and with Kybele Design Ops I helped make system usage visible across Turkcell teams.

Shaped the working rhythm

My manager handed the weekly design meetings to my peer and me. I introduced a brief standard and Trello task rules: an owner, a brief, a deadline, approved exports and a log of decisions.

Challenged the theme concepts

The agency’s concepts could not be maintained across themes. I said so in the review, was handed the project and rebuilt it on a color logic.

Took work from roadmap to release

The product team set the quarterly roadmap and briefs. I agreed the deadlines with them, set my own design priorities and took every item from brief to release.

Decisions 01

Make discovery easier

Responds to: One look on every visit

Listeners told us music helps them live a mood or move into one, and they wanted fizy to follow it. The app couldn’t: every visit showed the same page. We designed a modular homepage that can personalise for each listener, with moods and situations up front, so listening starts from how people feel.

Before

Homepage before the redesign
  1. The page looked the same on every visit, so there was little reason to explore.
  2. Recently played led the page, leaving few ways into new music.

After

Homepage after the redesign
  1. Modular sections that can change for each listener, so the page starts from what they like.
  2. Banners take their colour from the artwork automatically, so campaigns keep the page fresh.

Decisions 02

One clear listening experience

Responds to: Hard to find your way around

A redesign of function as much as looks. Playlist actions were scattered and unrelated, so I brought them into one context: a playlist card that holds every main action and stays consistent across artist pages, radios, user playlists and fizy playlists.

Before

Playlist before the redesign
  1. Main actions were scattered and unrelated across the page.
  2. The list showed little about itself, and offline sat in a separate toggle.

After

Playlist after the redesign
  1. One playlist card holds every main action, with shuffle built into play.
  2. Followers, songs and listening time are visible at a glance.

Decisions 03

Help people find what they want

Responds to: Search that needed the exact title

Search only worked when people typed the exact title, so many gave up or looked songs up elsewhere. We redesigned search to help at every step, with personal suggestions, popular searches and recent results, and I designed a new way to find a song by its lyrics.

Before

Search before the redesign
  1. Search opened on a plain list of recent queries, with nothing new to discover.
  2. Popular searches were text links, with no artwork to recognize them by.

After

Search after the redesign
  1. Search now opens with suggestions for you, so there is something to play before typing.
  2. Featured playlists and popular artists show their artwork, easy to recognize at a glance.

Decisions 04

Make people feel known

Responds to: One look on every visit

We wanted listeners to feel at home from the first minute, before they had played a single song. Onboarding builds a taste profile from the artists they pick, so the first homepage is already personal, not a generic starting point.

  • Onboarding: Pick at least three artists to start a taste profile

    Pick at least three artists to start a taste profile

  • Onboarding: Choices stay in view, so people see their profile take shape

    Choices stay in view, so people see their profile take shape

  • Onboarding: A clear finish that leads straight to a personal homepage

    A clear finish that leads straight to a personal homepage

  • Onboarding: Search for any artist, not only the suggestions

    Search for any artist, not only the suggestions

Decisions 05

Opening fizy to listeners beyond Turkcell

Responds to: A business goal: growing beyond Turkcell

Most fizy listeners already had it in their Turkcell bundle and paid nothing extra. To grow beyond Turkcell and stand as a brand of its own, fizy needed a way to earn from everyone else. I designed a free tier with audio ads, skip limits and song limits across the player and playlists, each with a clear path to Premium.

  • Free tier: Track list preview, so free listeners see what Premium unlocks

    Track list preview, so free listeners see what Premium unlocks

  • Free tier: Limited listening, with a clear path to Premium

    Limited listening, with a clear path to Premium

  • Free tier: Limited skips, explained before they run out

    Limited skips, explained before they run out

  • Free tier: Audio ads between songs, the trade for listening free

    Audio ads between songs, the trade for listening free

Decisions 06

One design system, every platform

Responds to: No system behind the screens

I started fizy’s design system on my own initiative, because the file mess and inconsistencies slowed every team down. I mapped the live flows, built the foundations as a symbol library with the components on top, and set naming rules modeled on Turkcell’s Kybele Design System. Every project in this case was built on it.

  • Color

    One palette with clear rules for text, backgrounds and actions.

  • Type

    One font family, down from two on mobile and three on web.

  • Spacing and radius

    Defined steps, so screens and components line up.

  • Icons

    An icon guide that cut the time spent searching for icons.

  • Components

    Buttons, cards and frameworks, with every state documented.

fizy design system sheets: colour guide, headline styles, list elements, navigation, playlist cards and icons

Decisions 07

Personal themes

Responds to: One look on every visit

Listeners asked for a more colorful app. The design system’s color symbols made personal themes possible, so listeners could choose how fizy looks. Themes has its own case study.

  • Homepage in the Original themePlaylist in the Original themePlayer in the Original theme

    Original

  • Homepage in the Rock Star themePlaylist in the Rock Star themePlayer in the Rock Star theme

    Rock Star

  • Homepage in the Coffee Love themePlaylist in the Coffee Love themePlayer in the Coffee Love theme

    Coffee Love

  • Homepage in the Love Story themePlaylist in the Love Story themePlayer in the Love Story theme

    Love Story

  • Homepage in the Sounds Green themePlaylist in the Sounds Green themePlayer in the Sounds Green theme

    Sounds Green

  • Homepage in the Party Time themePlaylist in the Party Time themePlayer in the Party Time theme

    Party Time

  • Homepage in the Sunset Dream themePlaylist in the Sunset Dream themePlayer in the Sunset Dream theme

    Sunset Dream

  • Homepage in the Deep Waters themePlaylist in the Deep Waters themePlayer in the Deep Waters theme

    Deep Waters

Learnings

What I learned in two years on fizy

  • Set success metrics before the redesign

    Research gave us clear signals, but we never agreed how to measure the releases against them. Next time I’d set metrics with the product team before the work starts.

  • Start the system before you need it

    I started a component library when I joined, long before anyone asked for a system. When the themes project came with a tight deadline, it gave us a base to build the full system on.

  • Bring design into the brief from day one

    Design joined the themes project late, after agency concepts that couldn’t be maintained across themes. Next time I’d make sure design is part of the brief from the start.

  • Document before you need it

    When I joined, there was no file of the live flows. I’d write the documentation earlier, so whoever comes next doesn’t have to start from scratch.

Hiring a senior product designer,
or want to talk design systems?