Build your own Spotify.

# Build an original app inspired by Spotify

You are an experienced product designer and full-stack engineer. Build a working, polished MVP from the brief below. Implement the core journeys end to end; a static mockup is not sufficient. Inspect the current environment, make sensible implementation decisions, and get started. Ask a question only if a missing answer genuinely blocks implementation.

Starting platform: Web. Explicit customized Product & audience and Tech stack requirements take precedence over this starting target.

## Product & audience
Build an original music library and player called Soundroom, inspired by Spotify. It is for people organizing and listening to music files they own or have permission to use. The main journey is importing audio, discovering tracks in the library, making a playlist, and playing it.

## Design
Use a rich, dark interface with a library sidebar, artwork-led album and playlist cards, and a persistent bottom player. Use a distinct original green accent, comfortable contrast, and a responsive queue drawer. Supply original placeholder album art.

## Features
1. Library: import supported local audio files; extract metadata when practical; otherwise let users edit track title, artist, and album. Validate file types and storage size.

2. Player: play, pause, seek, set volume, move previous/next, shuffle, repeat a track or queue, and show elapsed and total time. Start playback only after a user gesture.

3. Playlists: create, rename, reorder, duplicate, and delete playlists; add/remove tracks; show total duration and artwork derived from their contents.

4. Browsing: search tracks, artists, albums, and playlists; favorite tracks; show recently played tracks from actual listening activity.

5. Queue and persistence: display and reorder the queue, resume the last selected track without autoplay, and keep library metadata, playlists, and uploaded audio across reloads.

## Tech stack
Use the existing repository and conventions if there is one. If starting from scratch, use React with TypeScript and a practical, lightweight styling approach. Pick well-maintained libraries only when they materially help. Keep components, domain logic, and data access separate. Explain your chosen stack briefly, then begin implementation.

Follow the persistence requirements in Data & behavior. Personal tools may use IndexedDB. Products with public submission, bookings, permissions, or shared messaging require an authenticated backend with server-side authorization and durable storage. Use infrastructure already available in the environment. Do not put secrets in frontend code. If external infrastructure is unavailable, build a clearly labeled local demo, provide the schema and setup instructions, and state which shared features need configuration. Do not present simulated sharing or authentication as production functionality.

## Data & behavior
Track {id, title, artist, album, duration, mimeType, blobId, artworkId}; Playlist {id, title, description, trackIds}; LibraryFavorite {trackId}; PlayHistory {trackId, playedAt}; PlayerState {trackId, queueIds, position, volume, shuffle, repeat}. Store metadata and audio blobs in IndexedDB with quota handling. Use an HTML audio element and revoke object URLs when no longer needed.

Acceptance checks and scope:
Test queue advancement, repeat/shuffle rules, deleting a playing track, seek limits, storage exhaustion, and reload without automatic playback. Include only original, public-domain, or properly licensed sample audio. Do not scrape Spotify, reproduce its catalog, or suggest unauthorized access. Exclude paid subscriptions, recommendations requiring AI, and external streaming services.

## Originality and assets
The named product is a reference for general workflows only. Use an original product name, visual identity, wording, layout, and assets. Do not copy proprietary code, branded logos, distinctive screens, private APIs, paid templates, or protected media. Use original or appropriately licensed sample data and assets. Build from this brief rather than scraping the reference service. Do not imply affiliation with the referenced company.

## Implementation quality
- Make every visible control work, with clear loading, success, empty, validation, and failure states. Remove controls for unimplemented features.
- Support the target platform and responsive or resizable layouts where appropriate. Use platform-appropriate accessibility semantics, labels, keyboard operation, visible focus, sufficient contrast, and reduced-motion preferences. Provide alternatives for drag-only interactions.
- Validate inputs at the relevant boundary. Treat imported or user-generated content as untrusted; render it safely. Confirm destructive actions or offer undo.
- Keep state changes reliable across navigation and reloads. Never silently lose edits. Handle persistence and network errors with an actionable message.
- Keep the scope realistic. Prioritize the complete primary journey. If a custom Features section differs from the baseline, update the data model, design, and acceptance checks to match it; explicit custom requirements take precedence over baseline assumptions.
- Provide realistic original sample content and a useful empty state. Keep sample data clearly separate from user-created data.

## Delivery and verification
1. Inspect the repository and outline the implementation in a few sentences.
2. Implement the app and connect its actual data flow. Continue until the primary journey works.
3. Run appropriate checks and test the acceptance cases above on the target platform. Verify responsive layouts and keyboard navigation when browser tools are available. For native projects, build with the available SDK and test an emulator or device when possible; report any missing native verification honestly. For games, verify the rules and gameplay loop, not only the menus.
4. Fix observed failures, then provide the runnable result, setup/run instructions, a brief explanation of what is implemented, and any specific configuration or verification limits.

This is a focused MVP. Do not add billing, AI services, or unrelated features unless explicitly requested in the brief. Start building now.