Skip to content
All work
Mobile AppsFull case study

Audiosum

Audio-first learning, on the commute

An audio summaries app for people who want the substance of a long read in the length of a drive. I designed the full listening experience — discovery, player, queue, offline library and the subscription flow behind it.

Role
Lead product designer — research, UX, UI, prototype, handoff
Category
Mobile Apps
Industry
Media & Learning
Platforms
iOS, Android
Year
2025

The problem

What was actually wrong

Audio apps live or die on the first ninety seconds. Early testing showed people opened the app, saw a wall of categories, and closed it without playing anything. The product had a strong catalogue and no obvious way in.

The work

What I did, in order

  1. 01

    Ran a competitive teardown of eight audio and podcast apps to map what listeners already expect a player to do — and where the conventions could safely be broken.

  2. 02

    Rebuilt the home screen around one decision instead of many: a single 'ready to play' card sized to the time the listener actually has.

  3. 03

    Designed the player as a persistent mini-bar so navigating the catalogue never interrupts playback — the single most requested behaviour in testing.

  4. 04

    Mapped the download and offline states end to end, including the partial-download and expired-licence cases nobody had specced.

  5. 05

    Prototyped the paywall three ways and tested which framing people understood fastest before a line of it was built.

Key decisions

The three choices that mattered most

Every project has a handful of decisions that shaped everything after them. These were this project's.

Time-shaped discovery

Content is surfaced by how long the listener has — 5, 15 or 30 minutes — instead of by category. It matches how people actually decide what to play.

A player that never gets in the way

Mini-player, expanded player and lock-screen controls were designed as one component with three sizes, so state is never lost between them.

Honest offline states

Downloading, downloaded, paused, failed and expired each got a real design. Listeners on a train know exactly what they can still play.

What was delivered

  • User flows & information architecture
  • Low-fidelity wireframes
  • High-fidelity UI (iOS + Android)
  • Interactive prototype
  • Component library & tokens
  • Annotated developer handoff

Tools used

FigmaFigJamProtoPieMaze

Files were handed over annotated and component-based, with a live walkthrough for the engineering team.

Have a product like Audiosum?

Tell me what is not working. I will tell you honestly whether design is the right lever and what I would do in the first two weeks.

madnansakhi@gmail.com