We've gone through a lot of information in the past couple of chapters about intelligent caching. Let's pause and talk about some real-world scenarios that might affect the approach that you take in your own apps. We'll use the scenarios in Chapter 1, The Pain of Being Offline and apply what we've learned so far about offline development.

To facilitate the discussion, let's map each scenario to the following three axes:

Usage scenario axes

The three dimensions are Internet speed, Offline frequency, and Space on device. The more a scenario falls on the left-hand side of the graph, the more optimization we need to do. If the Internet speed is Slow, users are going to need caching to be highly prioritized: the most frequently viewed lists and text first and images and revision history last. If they're offline most of the time, the cache becomes sacred. Once gone, it's impossible to get it back. If their device is space-constrained, caching must be highly selective. Frequently viewed...