Offline Storage, Tracking, Debugging, and Optimization

  • John Percival


This chapter is focused on the increasingly important offline support for ads on mobile and tablet devices, on mandatory tracking, and on the tedious and often very time-consuming process of debugging in a browser and on a device. Offline support is becoming a requirement for many web apps, and advertising is quickly following suit. In this chapter, I’ll review how to handle offline events, detect when a user comes back online, and even discuss APIs that will detect when a user has a poor network connection. I’ll cover how to cache assets to client browsers and devices using HTML5’s AppCache API. I’ll also discuss tracking users’ interactions within advertising via tracking pixels and JavaScript, and I’ll use the methods to handle tracking calls and store calls in a client-side database using HTML5’s APIs. In addition, I’ll discuss the differences and browser support between the IndexDB API and the WebSQL API. I’ll also discuss APIs such as Lawnchair JS and how to handle cross-browser storing and caching as well as how to fire off tracking calls when a user is offline. Lastly, I’ll cover the detailed realm of debugging and optimization on desktop browsers and mobile devices. It’s a lot, so let’s get started.


Mobile Device Network Connection Client Browser Manifest File Event Listener 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

Copyright information

© John Percival 2013

Authors and Affiliations

  • John Percival

There are no affiliations available

Personalised recommendations