How f-loat/xiaoplayer works
Project type and purpose
• This is a WeChat Mini Program (“小程序”) called “卯卯音乐 (xiaomusic)” that acts as a client to play local or NAS-hosted music on Xiaomi AI speakers.
• It is a full-stack mobile-edge app using:
• A front-end Mini Program built with Weapp-Vite, TailwindCSS, Skyline rendering, and TypeScript.
• A set of serverless Cloud Functions (musictag, proxy, qrcode) running on Tencent Cloud.
• An external xiaomusic backend/service (user-provided NAS or IP-based music server).
File structure
• Top-level:
• cloudfunctions/… → multiple micro-endpoints (musictag, proxy, qrcode) each with its own package.json.
• miniprogram/… → WeChat Mini Program source (app.ts, pages/, components/, stores/, utils/).
• config/build files: vite.config.mts, tailwind.config.js, tsconfig.json, project.config.json, postcss.config.js.
• tooling: .eslintrc.js, husky pre-commit hook, prettier.
• Patterns:
• “miniprogram” directory follows the MVC-like page/component structure of WeChat apps.
• Cloudfunctions are pure API facades (stateless, single-responsibility).
Key insights from README
• Optional: user may configure the external xiaomusic service URL/IP (with optional basic auth).
• Cloudfunctions support local CORS-safe proxying and QR code generation for sharing.
1. WeChat Mini Program (Mobile App)
• Pages (index, list, player, setting)
• Components (search-bar, music-bar, device-list, lyric, time-bar, etc.)
2. Tencent Cloud Functions
• /musictag → metadata scraping
• /proxy → HTTP proxy for CORS & domain whitelisting
• /qrcode → generates QR codes
3. User-configured xiaomusic Service
• Music files (local/NAS)
• Playback API (HTTP interface)
4. Xiaomi AI Speaker (external device)
5. Developer Tooling (WeApp-Vite build & deploy)
• Mini Program → Cloud Functions (API calls to musictag, proxy, qrcode)
• Mini Program → xiaomusic Service (playback control, fetch track list, lyrics)
• Mini Program → Xiaomi AI Speaker via xiaomusic Service (push playback commands)
• Cloud Functions may call external metadata/tag services (for scraping)
• Build & Deploy Tooling → Cloud Functions / Mini Program (deployment pipelines)
c. Architectural patterns & principles
• Frontend-Backend separation (client vs. stateless serverless functions)
• Microservices style in Cloud Functions (single responsibility per endpoint)
• State management in Mini Program (modular stores)
• Custom routing & global toolbar (UI framework extension)
d. Technologies & frameworks
• Mini Program: Weapp-Vite, TailwindCSS, Skyline mode, TypeScript, WXSS, WXML
• Cloud: Tencent Cloud Functions, Node.js, package.json per function
• Build: pnpm, Vite, Tailwind, PostCSS, ESLint, Prettier, Husky