It's got some PWA'ism to it, but it doesn't prompt to install.

[Ominira]

• first off, you guys did/are doing awesomely well. MashaAllah tabarakallahu.
• I know there is already an Android app and an iOS app, but we could also have an installable PWA
• We could also make it relate to/reference the apps in playstore
• A custom install prompt dialog could also be added so no one will "freak out" about a website trying to install "something" on their phone or to their desktop.
• and some other cool features you guys are already probably aware can be done with PWAs.
• Would you like that I work on that?

[naveed-ahmad]

AsSalam o Alakim brother, please feel free to take this :) we had another issue related to service worker and PWA but not sure why @mmahalwy closed it. Related https://github.com/quran/quran.com-frontend/issues/894

[mustafa0x]

Chrome DevTools says: "Site cannot be installed: the page does not work offline".

[mmahalwy]

@naveed-ahmad reopened. we should have service workers on staging no? I don't have a ton of experience with it :(

[naveed-ahmad]

@mustafa0x that's because service worker isn't catching anything. We need to implement the offline first approach. Workbox is perfect candiate for us.

@mmahalwy yes, we'll have same service worker and manifest on staging and production. But we'll need to configure service worker on staging to only cache static assets and api calls for staging.quran.com.

We didn't have ssl on staging when we added manifest etc, but now its time to finally finish this feature :)

Empty SW: https://staging.quran.com/quran-service-worker.js Manifest: https://staging.quran.com/manifest.json

Resources we need to cache:

• All static urls ( css, js, fonts )
• Audio files
• All api calls

[Ominira]

Alright.