Appcache is an app packaging mechanism, and should be treated as such. The manifest is the equivalent of a plist or xml file describing the app package. It actu

Appcache is an app packaging mechanism, and should be treated as such. The manifest is the equivalent of a plist or xml file describing the app package. It actually makes a lot of sense when you view it like that. By extension, you should only put stuff into appcache that you would put in a native app bundle. I've built an appcache app that is a bunch of static javascript (in the CACHED section) contacting a bunch of services in the NETWORK section. There is no FALLBACK section, because any resource is either online or offline, but never both. The UI is designed so the user knows which content is online, and can decide for themselves if they have good enough connectivity. Dynamic content goes into localstorage if it needs to be persisted. This way of using appcache works very well and is mostly painless.