How herniezz/chronotune works
Project type and purpose
• This is a React single-page application (SPA) that displays playlists (static JSON), lets users choose music, play videos, and run a simple game with hearts and pop-up cards. There is no backend service; all data lives in public/playlist/*.json or in external video/analytics services.
File structure
• Top-level dirs/files:
• public/ – static assets, including playlist/*.json
• src/ – React source (App.js, components/, utils/)
• config.js – app configuration (e.g. API keys, endpoints)
• No server code, so architecture is purely client-side plus external dependencies.
Key components (to represent as nodes)
• Browser (user’s web client)
• Static JSON Store (public/playlist)
• dadrock.json
• elections.json
• top_teledyski.json
• React App
• Root: index.html → index.js → App
• Components:
– HomeScreen
– MusicChooseScreen
– GameForm
– GameScreen
– VideoPlayer
– PopUpCard
– Hearts
• Utilities: errorHandlers, reportWebVitals
• External services
• External Video Source
• Analytics Service
Relationships & data flows
• User clicks through HomeScreen → MusicChooseScreen
• MusicChooseScreen & GameScreen fetch playlist JSON from Static JSON Store
• VideoPlayer streams from ExternalVideo Source
• reportWebVitals sends metrics to Analytics Service
• Components communicate via props/context inside the React App
Architectural patterns & design principles
• SPA with component-based architecture
• Static asset hosting for playlists (no dynamic backend)
• Separation of concerns: UI components vs. utilities (errorHandlers, analytics)
• Externalized config in config.js