How harshsandhu44/mood-sync works
Project Type and Purpose
• This is a client-centric Next.js 13 “app router” project focused on generating and controlling audio in the browser.
• Purpose: let users select moods (e.g., calm, focus) and render corresponding soundscapes via the Web Audio API (and optional libraries like Tone.js or p5.js).
File Structure
• Top-level Next.js config files (next.config.ts, postcss.config.mjs, eslint.config.mjs) govern build & linting.
• public/ contains static assets (manifest, browserconfig).
• src/app/ holds Next.js page and layout components (app router).
• src/components/ contains:
– Core UI: MoodSelector, SoundTypeSelector, AudioControls, AudioVisualizer, PlaybackButton, SafetyWarning, etc.
– Providers: root-provider (app-wide context), theme-provider.
– UI primitives: accordion, button, dialog, slider, etc. (your custom component library).
• src/hooks/ encapsulates logic: useAudioEngine (bridges UI to Web Audio API), use-mobile, useCustomStyles.
• src/lib/ utilities (fonts loading, generic utils).
• src/constants/ (moodFrequencies.ts) holds mapping of moods→frequencies.
• src/types/ defines TypeScript types for audio and application data.
Pull Architecture Insights from the README
• Entire audio graph runs in the browser via Web Audio API (possibly augmented by Tone.js or p5.js).
• UI/UX emphasizes mood selection → algorithmic sound generation.
• No server-side API routes—only static generation/SSG or SSR for pages. All audio logic is client-side.
Main Components & Relationships
a. Components:
• User’s Browser (client environment)
• Next.js App Router & Page/Layout (entry point)
• React Component Tree (MoodSelector, AudioControls, AudioVisualizer, etc.)
• Context Providers (theme, root state)
• Hooks/Services Layer (useAudioEngine orchestrates audio graph; useCustomStyles for theming; etc.)
• Web Audio API (AudioContext, OscillatorNode, GainNode, Filters)
• (Optional) Audio Libraries: Tone.js or p5.js add higher-level scheduling or synthesis features
• Static Assets & Constants (CSS, images, moodFrequencies, fonts)
b. Interactions & Data Flows:
1. User interacts with UI → triggers React handlers.
2. Handlers invoke custom hooks (useAudioEngine) through context.
3. Hook builds/updates an AudioContext graph (oscillators, binaural beats, isochronic tones).
4. Web Audio API outputs sound to client device.
5. UI reading of state (e.g., current frequency, playback status) flows back via context to re-render controls & visualizer.
c. Architectural Patterns:
• Component-based architecture (atomic UI components + providers).
• Hook-driven service layer encapsulating side-effects (audio generation).
• Next.js App Router for page/layout composition.
d. Key Technologies & Frameworks:
• Next.js 13 (React 18, App Router)
• TypeScript
• Web Audio API
• Custom React Hooks
• Tailwind/PostCSS (global styling)
• UI primitives (Radix-style components)
• Optional: Tone.js, p5.js for advanced synthesis