How polovni/jammming works
Project type and purpose
• This is a single-page front-end web application bootstrapped with Create React App.
• It provides a UI for searching songs (via an external music API, e.g. Spotify) and building a playlist in the browser.
File structure
• Top-level “public” folder holds static assets (index.html, manifest.json, redirects).
• “src” folder contains:
• App.js / App.css – the root component and styles
• index.js – ReactDOM entry point
• reportWebVitals.js, setupTests.js, and test files – testing and performance hooks
• Two feature subfolders:
– searchComponents: Input, SearchBar, SearchResults (plus tests)
– songComponents: Track, Playlist (plus tests)
• package.json defines scripts (start, build, test), dependencies (React, Jest), and build tools (webpack, Babel via CRA).
README
• Confirms standard CRA setup
• No custom backend—everything is client-side
• Build and deployment instructions target a static host
Core components
a. Browser/client
• React app bundle served to the client
• Components: App → SearchBar + SearchResults + Playlist + Track
b. Static asset server (CDN or static-site host)
• Serves index.html, JS/CSS bundles
c. Build pipeline (Node/npm, webpack, Babel)
• Transpiles & bundles src into production assets
d. External music API service
• Handles search requests and returns JSON song data
Relationships and data flow
• User → Browser UI (SearchBar input)
• UI (App) → External API via fetch/axios (search query)
• API → UI: JSON searchResults
• UI: App state updated → SearchResults component renders Tracks
• User selects tracks → App state updated → Playlist component renders tracks
• (Optional) On “Save playlist”: App → External API (POST playlist)
Architectural patterns & design principles
• Component-based design (React)
• Unidirectional data flow (App holds state, passes props down)
• Separation of concerns: presentation vs. container logic
• Testability: each component has a corresponding test file
Relevant technologies/frameworks
• React, ReactDOM
• Jest + React Testing Library
• Webpack, Babel (under the hood via CRA)
• Node.js/npm scripts
Key takeaways
• Essential elements (UI, state container, external API, build & deployment)