This will aggregate playlist and artwork data so the client only needs to make two requests for both. Currently, the client can make up to five requests for this information.
The backend service can also provide links to the track on other services: Spotify, Apple Music, Google Play, Pandora, Bandcamp, and others.
This should exist as its own project. Either we should extract all the webby bits in the current app so that it can run in a Linux box without the presence of Foundation, or we start from scratch on a server platform that doesn't use Swift (Python and Java come to mind, with whatever server frameworks they use; I'm just a mobile engineer).
This will aggregate playlist and artwork data so the client only needs to make two requests for both. Currently, the client can make up to five requests for this information.
The backend service can also provide links to the track on other services: Spotify, Apple Music, Google Play, Pandora, Bandcamp, and others.
This should exist as its own project. Either we should extract all the webby bits in the current app so that it can run in a Linux box without the presence of Foundation, or we start from scratch on a server platform that doesn't use Swift (Python and Java come to mind, with whatever server frameworks they use; I'm just a mobile engineer).