Load part of the history list and load the rest as you scroll down the list.

Loading a large history list results in a large number of network calls. We could reduce this by only loading a few episodes and requesting more as the user scrolls. This is especially noticeable on a first sync.

Start by tracing the history list and the first-sync network-loading path in the Android project; the issue does not name specific files or tests. Determine how the list currently requests episodes, then verify that the initial load fetches only a few episodes and that scrolling requests the remainder with fewer calls overall.

Written by the indexing model from the issue text.