# Discourse as a Progressive Web App

**URL:** <https://meta.discourse.org/t/discourse-as-a-progressive-web-app/47265>\
**Category:** Feature\
**Created:** [14 Luglio 2016, 12:40am UTC](https://meta.discourse.org/t/discourse-as-a-progressive-web-app/47265 "2016-07-14T00:40:59Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![fefrei](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/fefrei/32/119538_2.png) [@fefrei](https://meta.discourse.org/u/fefrei)\
**Post date:** [16 Luglio 2016, 7:55am UTC](https://meta.discourse.org/t/discourse-as-a-progressive-web-app/47265/16 "2016-07-16T07:55:45Z")

</div>

One huge drawback of AppCache is that it’s caching exactly one block of data. This must obviously contain the Discourse “App”, and shouldn’t contain _all_ posts (of course), so the actual data (the posts to be cached) has to be put into something like localStorage, which seems to be often limited to 5 MB.

(I have some experience with AppCache as I have built [one webapp](https://pseuco.com/#/landing) with it. AppCache is unflexible, confusing and punishes you for any mistake you make, but works pretty well if used correctly.)

---

_[View the full topic](https://meta.discourse.org/t/discourse-as-a-progressive-web-app/47265)._
