How jesusalberto11/mymusicplayer works
Main Components
• Frontend (React SPA)
– src/ folder: UI components, pages, hooks, state (Zustand), routing (React Router), i18n.
– Audio engine: HTML5 audio element controlled by React.
• Desktop Runtime (Tauri)
– Tauri bridge (JavaScript↔Rust IPC) configured in src-tauri/tauri.conf.json.
• Backend (Rust)
– src-tauri/src/main.rs: commands exposed to the frontend.
– id3 crate: reads file metadata.
– build.rs: any build-time file operations.
• File System Storage
– Local music directory (MUSIC_PATH) containing .mp3 files.
– Cover images folder and image‐path template (SONGS_COVERS_FOLDER, SONGS_IMAGES_PATH).
• External Services (optional)
– No external web services; all data is local.
Relationships & Data Flows
• Startup Flow
1. React app initializes (main.tsx → App.tsx).
2. Calls Tauri command “loadSongs” via JS API.
3. Rust scans MUSIC_PATH, parses ID3 tags, returns song list with metadata & cover paths.
4. Frontend stores list in MusicPlayerStore/PlaylistsStore.
• Playback Flow
1. User clicks play in UI.
2. React invokes HTML5 audio API directly.
3. UI updates current song state via Zustand; controls (VolumeControl, ProgressBar) reactively update.
• Settings & Playlists
– UI components (SettingsPage, PlaylistsPage) read/write state in stores; persist playlists in memory or local storage if configured.
Architectural Patterns
• Layered Separation
– Presentation: React components & CSS.
– State: Zustand stores.
– System/API: Tauri commands (Rust).
• MVVM-like data binding via hooks (useMusicPlayer, usePlaylists)
• Local Persistence = File System (no external DB)
• IPC Boundary: clear JS ↔ Rust separation via Tauri.
Call Out Key Technologies
• Frontend: React, React Router, React i18Next, Zustand, Vite, TypeScript, CSS Modules.
• Backend: Rust, Tauri, id3 crate, Cargo.
• Build & Config: Cargo.toml, build.rs, tauri.conf.json, .env for paths.