IF traffic is widespread through the day and app is doing 1 request per day. If traffic concentrates in some hours request ratio might be higher
It largely boils down to "it depends" on:
- Number of "Top read sections" that are in the user's feed on that device
- Which sections they scroll to (we fetch lazily)
- Whether the app is ever purged from memory (i.e. terminated by the OS)
The app will keep previous pageviews responses in memory, so as long as the app lives, it won't make another request until it reaches the next day, and attempts to fetch pageviews data for it.
We would also like to double check that caching headers are respected in the app and requests are not retried if they are mean to be cached. Can developers confirm this is the case?
We can look into it, but it might not really be necessary in practice since we'd only re-fetch data if the app was forcibly terminated by the user or OS, and the user scrolled to view older sections of the feed. IOW, persistenting previous responses to disk with cache control information will only save user data (and server bandwidth) in the off chance that our existing in-memory data is purged.
That said, iOS already does have mechanisms for respecting HTTP cache control headers. We just need to (finally) take advantage of them.