- To test knowledge of consuming APIs and handling responses
- Loading state and knowing where and how to make multiple API calls efficiently
- Add your Spotify client ID & secret to
config.js
- Note. Never add this type of config to version control. This would usually come from your build server.
- Fetch and display Released This Week songs
- Use the API path
new-releases
- Use the API path
- Fetch and display Featured Playlists
- Use the API path
featured-playlists
- Use the API path
- Fetch and display Browse genres
- Use the API path
categories
- Use the API path
- Loading state/UI (optional, current UX is already clean)
- 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?
- UI/UX for all elements, including previews (mobile responsive)