In the last chapter, we put our fledgling app online. Currently, it's a bit tone-deaf. We don't communicate anything that's happening under the hood so there's a lot of is it working? I really hope it's working. We also don't attempt to compensate for bad network connectivity. In this chapter, we'll address both of these concerns.

A lot of what differentiates a bad offline experience from a good offline experience is the way an app communicates with people. With two functionally-equivalent apps, the one that comes across as most transparent and honest will win every time. This is particularly important in a first impression scenario. Over time, you may learn to accommodate an app's quirks and foibles, but if people don't stick around after their first bad experience, you've lost.

Fortunately, PouchDB gives us a lot of information about what's happening. We've ignored these events thus far, but in this chapter, we'll be able to pass this information...