# Discourse as a Progressive Web App

**URL:** https://meta.discourse.org/t/discourse-as-a-progressive-web-app/47265
**Category:** Feature
**Created:** [July 14, 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:** 2
**Page:** 2

<div class="post-metadata">

### Author: ![eviltrout](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/eviltrout/32/5275_2.png) [@eviltrout](https://meta.discourse.org/u/eviltrout)
#### Post date: [January 25, 2017, 8:11pm UTC](https://meta.discourse.org/t/discourse-as-a-progressive-web-app/47265/22 "2017-01-25T20:11:37Z")

</div>

Yeah, it’s not the best choice to make, but at least AppCache works everywhere, despite being deprecated.

The deprecation is particularly bad because Mozilla knows that Safari doesn’t support Service Workers.

---

<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: [January 30, 2017, 10:26pm 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.

🙂

[Previous page](https://meta.discourse.org/t/discourse-as-a-progressive-web-app/47265.md?page=1)