How shubham-raj-dev/melodyone works
MelodyOne is a music discovery and streaming application with a Next.js frontend and Python APIs. A principal workflow searches for a track, returns metadata and a preview stream, then hands playback to shared player state and player UI. Users can also authenticate and save liked songs; separate API modules provide YouTube audio lookup and SQLite-backed playlists/favorites. The repository contains distinct Flask implementations, so their routes are shown separately rather than treated as one wired service. Some frontend relationships are documented capabilities or remain unverified in sampled source.
Main entry points: run.py Search and library routes · Search.tsx Track search · player-store.ts Player state · views.py Media API routes
Components 17
Web experience
- Next app shell
frontend/src/app/layout.tsx - Track search
frontend/src/pages/Search.tsx - Clerk identity
frontend/src/app/sign-up/[[...sign-up]]/page.tsx
Playback
- Player state
frontend/src/store/player-store.ts - Player controls
frontend/src/components/RightSidebar.jsx - Mobile player
frontend/src/components/MobileBottomPlayer.tsx
Music APIs
- Search and library routes
backend/run.py - Media API routes
backend/api/views.py - YouTube audio lookup
backend/api/ytdlp_engine.py - Extractor settings
backend/api/config.py
Personal library
- Mongo user store
- Playlist and favorite data
backend/api/models.py - SQLite catalog
backend/api/config.py
Other components
- Listener
- Apple catalog
- Lyrics service
- Clerk service
Connections 15
- Listener → Track search: searches
frontend/src/pages/Search.tsx - Track search → Search and library routes: requests tracks
frontend/src/pages/Search.tsx - Search and library routes → Apple catalog: queries catalog
backend/run.py - Search and library routes → Mongo user store: reads and updates
backend/run.py - Search and library routes → Lyrics service: fetches lyrics
backend/run.py - Track search → Player state: sets song
frontend/src/pages/Search.tsx - Player state → Player controls: drives playback UI
- Player state → Mobile player: drives playback UI
- Listener → Clerk identity: signs in
frontend/src/app/sign-up/[[...sign-up]]/page.tsx - Next app shell → Clerk service: provides identity
frontend/src/app/layout.tsx - Media API routes → YouTube audio lookup: calls lookup
backend/api/views.py - YouTube audio lookup → Extractor settings: uses options
backend/api/ytdlp_engine.py - Media API routes → Playlist and favorite data: calls data operations
backend/api/views.py - Playlist and favorite data → SQLite catalog: reads and writes
backend/api/models.py - Listener → Next app shell: browses
README.md