You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To test knowledge of consuming APIs and handling responses
Loading state and knowing where and how to make multiple API calls efficiently
Pre-requisites ✅
Add your Spotify client ID & secret to a .env file in root using the environment variables REACT_APP_SPOTIFY_CLIENT_ID and REACT_APP_SPOTIFY_CLIENT_SECRET
Note. Never add this type of config to version control. This would usually come from your build server.
Requirements 📖
Fetch and display Released This Week songs
Use the API path new-releases
Fetch and display Featured Playlists
Use the API path featured-playlists
Fetch and display Browse genres
Use the API path categories
Loading state/UI (optional, current UX is already clean)
Think about 💡
Taking a look at the Spotify API documentation
Do you resolve each API request one after the other or in parallel?
Where do you make the API requests?
How much logic do you offload out of the UI components?
What's Already Been Done 🏁
UI/UX for all elements, including previews (mobile responsive)