The remote API is not designed for easily fetching all the necessary information in a reasonable number of calls. For example, to fetch n videos in a category, the category needs to be fetched (1 call), details about each video need to be fetched (n calls), and the streaming links (information about the actual video URL) need to be fetched for each video (n calls). Even more calls may need to be performed to support other use cases, e.g., search.
Consider whether or not the app, from a development point of view, becomes significantly simpler if the API is called every time information is needed. To avoid fetching the same information multiple times, caching using Retrofit could maybe prove useful.
The remote API is not designed for easily fetching all the necessary information in a reasonable number of calls. For example, to fetch
n
videos in a category, the category needs to be fetched (1
call), details about each video need to be fetched (n
calls), and the streaming links (information about the actual video URL) need to be fetched for each video (n
calls). Even more calls may need to be performed to support other use cases, e.g., search.Consider whether or not the app, from a development point of view, becomes significantly simpler if the API is called every time information is needed. To avoid fetching the same information multiple times, caching using Retrofit could maybe prove useful.
API: http://www.dr.dk/mu-online/Help/1.3