How foamzou/melody works
Main System Components
a) Frontend Layer:
• PC Interface (Vue.js based)
• Mobile Interface (PWA-enabled)
• Shared Components (Player, Search Results, Task Notifications)
b) Backend Layer:
• API Server (Node.js)
• Service Modules
• Media Processing
• Platform Integration
c) External Services:
• Music Platforms (NetEase Cloud Music, etc.)
• Media Sources (Bilibili, Douyin, etc.)
Component Relationships
[Frontend Layer]
• ↑↓
[Backend API Layer]
• ↑↓
[Service Layer]
• ↑↓
[External Services]
Detailed Component Breakdown
• PC Views
• Home
• Account
• Playlist
• Settings
• Mobile Views
• Home
• Account
• Playlist
• Shared Components
• Player
• Search Results
• Task Notifications
• API Handlers
• Account Management
• Playlist Management
• Song Management
• Media Fetching
• Sync Jobs
• Services
• Media Fetcher
• Music Platform Integration
• Search Service
• Sync Service
• Config Management
• Music Platforms
• Media Sources
• Storage (Cloud Drive)
Data Flow Indicators
• User requests flow (frontend → backend)
• Media processing flow (external → backend → frontend)
• Storage operations (backend → cloud storage)
• Authentication flow (user → frontend → backend → music platforms)
Technical Stack Indicators
Technology labels:
• Frontend: Vue.js, PWA
• Backend: Node.js
• External Tools: FFmpeg
• Deployment: Docker
Mobile/PC interface separation
Keep the abstraction level focused on the main architectural components while showing the key interactions that make the system unique, such as the music unlocking feature and cross-platform media fetching capability.