LumaMusic

LumaMusic Product Specification

Status: Phase 1 baseline
Owner: PauzeDevs
Platforms: Android and iOS
Initial music source: Audius

Product vision

LumaMusic is a modern music discovery and listening app with a refined, editorial interface. It should feel fast, calm, personal, and music-first. The first release must accurately represent the music available from connected sources; it must not imply that Audius contains every mainstream or charting release.

Product principles

  1. Playback reliability first.
  2. Honest catalogue presentation and track-level availability.
  3. Fast discovery with designed loading, empty, and error states.
  4. Personal library with clear separation between local app actions and Audius account actions.
  5. Native behaviour for audio focus, interruptions, background playback, headset controls, and lock-screen controls.
  6. Accessibility: readable contrast, scalable text, screen readers, and comfortable touch targets.

Primary bottom navigation:

Persistent player:

Secondary destinations: track details, artist profile, playlist details, album/collection details where supported, queue, settings, and Audius attribution information.

MVP features

Home and discovery

Playback

Library

Artist and collection pages

Settings

Native audio behaviour

Release target: background playback, lock-screen metadata and controls, headset/Bluetooth controls, audio focus and interruption handling, and correct behaviour around calls and alarms. These are acceptance requirements, not claims that they are already implemented. The audio engine will be selected after a native proof of concept.

Later features

Explicit non-goals

The first release will not claim the full Spotify, Apple Music, or YouTube Music catalogue; scrape or extract audio from those services; bypass subscriptions, ads, DRM, geographic restrictions, or playback controls; download/cache tracks without permission; re-host third-party music files; or promise lyrics, lossless audio, or a bitrate without verified support.

Core user journeys

Discover and play

  1. User opens Home.
  2. App loads discovery sections.
  3. User selects a track.
  4. App checks availability and requests the permitted stream.
  5. Playback starts and mini-player appears.
  6. User opens Now Playing and manages the queue.

Search and play

  1. User enters a query.
  2. Search is debounced.
  3. Track / artist results appear with loading and error states.
  4. User selects a playable track.
  5. Playback begins and queue state updates according to defined queue rules.

Save a favourite

  1. User taps like.
  2. Local library updates immediately.
  3. The change persists locally.
  4. Audius account sync, if added later, requires explicit OAuth authorization.

MVP acceptance criteria

First-test success measures