We never considered the case in the Track Tab where there are more than 350 tracks. (The backend already handles this, just not the front-end).
Example Playlist (2500 tracks): https://app.artist.tools/playlist/6GXmBjU087g6BTLrQhAZVq
Will need to find a way to support paginating a huge list of tracks elegantly.
Currently, we load all tracks at once to support things like:
- total stream count
- avg popularity in playlist
Initial thoughts
- load all the data in the backend
- getting avg. popularity on 2500 songs means 50+ API calls
- if client receives 2500 songs at once, it may crash. paginate client?