Persona: Alex — the multi-format listener
Primary persona. Alex listens to music daily, podcasts weekly, and occasionally audiobooks. They want one app that adapts to each type of listening rather than three separate apps.
Persona: Alex — the multi-format listener
Primary persona for v1. Drives the Music Room, Home (Lobby), and core playback experience.
Demographics
| Role / title | Knowledge worker, mid-30s |
| Product experience | Intermediate — comfortable installing desktop apps and configuring settings |
| Technical skill | Low–Medium — can copy a plugin to a directory, will not write one |
| Domain expertise | Music listener since adolescence, subscribes to 2 streaming services, has a local FLAC collection |
| Tools they use daily | Spotify, VLC, a podcast app, browser, messaging |
Goals
- Listen to music from all sources (Spotify, local files) in one place with a consistent, music-optimized interface.
- Switch between music and spoken-word content without losing their place or changing apps.
- Discover new music through search that spans all their content sources at once.
- Save tracks to playlists and access them regardless of which source they came from.
Pain points
- App fragmentation: Uses Spotify for streaming, VLC for local FLACs, and a separate podcast app. Switching between them is friction.
- One-size-fits-all UI: The podcast app’s UI is wrong for music (episodic layout, show-focused navigation). The music app’s UI is wrong for audiobooks (no progress tracking, no chapter support).
- Scattered library: Favorites exist in Spotify, local playlists in VLC. No unified view of saved music.
- Search fatigue: Has to search Spotify, then search local files separately. No cross-source search.
- Plugin installation friction: Willing to install plugins if it’s “download and forget.” Will not edit config files or run terminal commands to get started.
Behaviours
- Discovers new apps through forum recommendations and Reddit.
- Evaluates a tool by trying it on their existing music collection first (local files).
- Prefers learning through a quick-start guide and intuitive UI. Will not read a 40-page manual.
- Expects audio apps to “just work” — install, point at music, listen.
- Will tolerate one-time setup if the result is a better daily experience.
Scenarios
Primary scenario: First-run experience
Context: Alex downloads Rymflux after hearing about it on a forum. They have a large FLAC collection and a Spotify subscription.
Goal: Get music playing within 5 minutes of first launch.
Success criteria:
- App launches and shows a “Getting Started” guide or empty state that clearly explains what to do.
- Alex points the local-files plugin at their music directory in under 2 minutes.
- Songs appear in the Music Room browse view immediately.
- Alex plays a track and hears audio.
Secondary scenario: Daily listening
Context: Alex has used Rymflux for a week. They have the local-files plugin and a streaming plugin (e.g. Jamendo) installed.
Goal: Find and play a specific track from either source without checking which source has it.
Success criteria:
- One search query returns results from both plugins, deduplicated.
- Alex can add tracks from both sources to the same queue.
- The queue plays through both Spotify streams and local files without interruption or quality difference in UX.
Secondary scenario: Room switching
Context: Alex is listening to music and wants to check their audiobook’s progress.
Goal: Switch from Music Room to Audiobook Room (v2) without stopping music.
Success criteria:
- Alex navigates to the Audiobook Room.
- Music continues playing.
- Audiobook Room shows current book, chapter, and progress.
- Switching back to Music Room is instant.
Quotes
“I don’t want one app for streaming, another for my downloads, and a third for podcasts. I want one app that understands what I’m listening to.”
Validation
| Aspect | Status |
|---|---|
| Based on user research | Partial (common patterns observed in media app usage) |
| Last validated | Charter phase — persona derived from vision-of-rooms-design.md |
| Primary persona for which features | Music Room, Home (Lobby), core playback, queue, library, plugin discovery |
Related
- Journey map: Listener music journey
- User stories: Play music, Search across sources, Save to library
- Other personas: Plugin developer