How robertsolorzano/track-match-client works
Project type and purpose
• This is a React Native mobile application, scaffolded with Expo (app.json, eas.json, babel.config.js).
• Its purpose is to let users search Spotify, browse their library, and view track details in a native mobile UI.
• It relies on the Spotify Web API (now deprecated) and includes a Firebase config (firebaseConfig.js) for any user-data or auth interactions.
File structure
• Top-level files:
• App.js – the app’s entry point
• package.json / package-lock.json – Node dependencies
• babel.config.js – transpilation settings
• eas.json – Expo Application Services build config
• firebaseConfig.js – Firebase SDK setup
• “app/” directory:
• app/navigation/ – React Navigation setup (BottomTabNavigator.jsx, LibraryStackNavigator.jsx, SearchStackNavigator.jsx)
• app/screens/ – Screen-level containers (Homescreen, LibraryHomeScreen, LibraryDetailsScreen, SearchScreen, SongInfoScreen)
• app/components/ – Reusable UI widgets (SearchBar, TrackDisplay, AudioPlayer, AlbumArt, etc.)
• app/utils/musicUtils.jsx – Spotify API request helpers, data formatting
• No backend directory – all logic lives in the client; external services handle data persistence / retrieval.
README
• Minimal content: “Spotify has now deprecated most APIs that was needed for this project.”
• Indicates that the core external dependency (Spotify API) is no longer available, but the architecture remains a good reference for UI → API integrations.
a. Main components
1. Client App (React Native / Expo)
• Navigation Layer
• Screens
• UI Components
• Business-logic utils
2. External Services
• Spotify Web API
• Firebase (Realtime Database / Auth)
3. Build / Deployment
• Expo EAS Build
• babel transpiler
b. Relationships & data flows
• User taps UI Components → triggers Navigation → loads Screen
• Screens compose Components and call musicUtils → HTTP requests to Spotify API
• auth flows or data persistence via firebaseConfig → Firebase SDK
• Expo CLI/EAS picks up App.js + dependencies → builds native binaries
c. Architectural patterns & design principles
• Layered client architecture:
– Presentation (Components)
– Container (Screens)
– Routing (React Navigation)
– Services/Utils (API wrappers)
• Single responsibility per component
• Separation of concerns between navigation, UI, and data-fetch logic
d. Key technologies & frameworks
• React Native + Expo
• React Navigation
• Spotify Web API
• Firebase JS SDK
• EAS Build, Babel