# Discourse as a Progressive Web App

**URL:** <https://meta.discourse.org/t/discourse-as-a-progressive-web-app/47265>\
**Category:** Feature\
**Created:** [2016 年 7 月 14 日午前 12:40 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:** 23

<div class="post-metadata">

**Author:** ![kirupa](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/kirupa/32/374711_2.png) [@kirupa](https://meta.discourse.org/u/kirupa)\
**Post date:** [2017 年 1 月 30 日午後 10:26 UTC](https://meta.discourse.org/t/discourse-as-a-progressive-web-app/47265/23 "2017-01-30T22:26:42Z")

</div>

While AppCache is more broadly supported, future device integrations around Progressive Web Apps will check for the existence of a Service Worker. I’m not saying whether that is a good idea or not, but that’s what browser vendors have decided on. You won’t see the “Install…” badge on Chrome, for example, without the app having both a service worker and Web App Manifest.

That’s why it would be nice to have discourse use Service Workers when available or use AppCache for devices that don’t support it.

🙂

---

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