HTML and CSS Reference
rather quickly and be implemented immediately so that adoption takes rapidly. Only then will you be able to offer
accurate network connection detection and provide rich offline experiences.
■ if your ad requires offline availability, make sure to remove any Ctas around tap because there will be no
network when viewing ads offline, so users will not be able to view pages.
In this section, I'll cover an offline web application specification and how to work with application caching.
This section is geared toward publishers and content owners looking to bring offline support to their web applications.
In HTML5, application caching is supported by creating a simple manifest file, which lists the assets to be used for
the application offline. These assets are the files needed to be stored to the users' browser in order to render correctly
without any Internet access. Before we dig in deeper, keep in mind that caching all the assets to a user's browser could
result in very long caching times as well as a bloated manifest document, so choose your storing wisely.
When a user views the document without network access, the browser switches to use the local cached assets in
its place. So, in theory, the user should be able to finish interacting with that game or watching that video spot while on
the subway or on a plane with no in-flight WiFi, assuming the application cache stored the files to the device correctly.
With strong browser support, especially in the mobile realm, this is something you can start taking advantage of
immediately. Figure 10-1 outlines the tremendous support for the application cache as of November 2012.