Back

yap · Product Design · 2026

Organizing Voice Chats Around Topics, Not Timelines

Role Solo Designer
Timeline 2 weeks · Jun 2026
Platform Voice Chat App Concept
Scope Product Design · Interaction Design · Prototyping

Overview

Voice conversations drown in chronology.

Most messaging apps treat voice chats as ephemeral—quickly lost in the feed as new conversations pile up. But voice conversations often cover multiple topics across long sessions. The problem: timelines, not topics.

Problem

Users can't reference past points from voice conversations. There's no way to organize long calls by subject or find what was discussed when.

Opportunity

What if users could mark segments of voice conversations by topic? Timestamps become searchable, conversations become navigable.

How might we make voice conversations queryable and navigable by topic?

Solution

Topic markers: organize voice chats as they happen.

During a call, users tap to mark topic shifts. The app generates a searchable outline of the conversation.

Topics reshape how we search conversations.

After the call, the conversation outline makes it easy to jump to the discussion you need.

Core Flows

The system had to be lightweight, not disruptive.

Users needed to mark topics without leaving the call experience. A single tap, then name the topic.

Marking happens in the background

A button in the call interface lets users add topic markers without pausing the conversation.

After the call, the outline appears

Participants see a structured view of what was discussed. Click any topic to jump to that timestamp.

System

Designed for minimal friction.

The system works because it lives inside the existing call interface, not as a separate feature.

Before Topics

Long voice calls become a single, unsearchable artifact.

With Topics

Conversations become navigable outlines you can reference forever.

System map showing topic markers as a layer across the voice chat interface

The value comes from turning ephemeral conversations into structured reference materials.

Research

Voice conversations are harder to reference than text.

Users struggle to find specific moments in past calls and often re-record audio to document decisions made during calls.

User interview synthesis: pain points with voice messaging

Voice is rich but searchless

Audio captures tone and nuance, but you can't search it or skim it the way you can with text.

Long calls blur together

Users can't remember what was discussed when, only that it happened sometime during a call.

Context gets lost

Without structure, the most important moments of a conversation can be forgotten or hard to locate.

Competitive analysis: how other platforms handle long-form audio

Design Decisions

The feature had to feel native to voice calls.

Most important decisions were about minimizing cognitive load and keeping focus on the conversation.

Structural fit

The marker button lives in the call controls, accessible without breaking the flow of conversation.

System map: topic markers integrated into call UI

Keep markers lightweight

A single tap to mark, a quick voice label after. Minimal friction.

Show the outline after

Participants see the structure when the call ends, when they're ready to reference it.

Navigation fit

The outline interface mirrors messaging app patterns so users know how to navigate it.

Topic outline mimics familiar list navigation patterns

Simple, scannable outlines

Show topic name and timestamp, let users jump directly to segments.

Allow flexible labeling

Users can name topics however makes sense to them, not constrained by a taxonomy.

Impact

Success is whether users reference past conversations.

The feature works if topic markers make users more likely to jump back into old calls to find information.

Primary metric

Engagement with historical call outlines and topic-based playback.

Secondary metrics

Marker adoption rate, average markers per call, re-reference frequency.

Next step

Test with user groups, measure whether topic markers actually reduce the need for follow-up text messages.

If this works, it could transform how teams document decisions made in real-time conversation.

Reflection

Structure emerges from behavior.

This project taught me that the best organizational systems don't require separate work—they integrate into what people are already doing. Voice conversations don't need transcription or tagging workflows. They just need one natural moment to mark what matters.

Timing is everything

The moment to organize is when something feels important, not after the fact.

Simplicity scales

A single tap beats any complex tagging system—if it lives where the behavior happens.

Voice is underrated

Most design treats voice as a fallback. But it's richer than text if we structure it right.