IO Question: How are you dealing with AppCache relatively small storage limits?

This content originally appeared on Modern Web Development with Chrome and was authored by Paul Kinlan

<p>We had an <a href="http://goo.gl/mod/NSEW">awesome question</a> for our Google IO talk - <a href="http://io2011-zerotohero.appspot.com/index.html#1">Mobile Web Development: Zero to Hero</a> - that we didn't get time to answer live.<p /><div>How do we deal with the storage constraints imposed by modern browsers.  The answer is simple, App Cache is used mainly to store program code, that is just the CSS and JS (and also the page that requests the AppCache), our application never got that large.</div> <p /><div>We did make some basic optimisations, our production version ran compressed JS code - our <a href="https://github.com/PaulKinlan/ioreader/raw/master/run.sh">build process minified the JS</a> using uglifyJS.  We had the option to compress the CSS (but we chose not too for ease of development).  But in all honesty, our application never got that large.</div> <p /><div>If we struggled for space we would have moved into only AppCaching the form-factor specific code and assets, but it wasn't required.</div></p>

This content originally appeared on Modern Web Development with Chrome and was authored by Paul Kinlan