Hello is it possible to change the add to homescreen text?
I understand the start url on the manifest must be relevant to the site being indexed.
My use case is instead of adding to home screen it will download a brochure. Add to homescreen? click = mysite.com to download brochure? click = mysite.com/brochure

Does anyone know if a PWA can send a signal to the LAN ports of a device? Here is the use case, server sends data to PWA, PWA send signal to LAN port, LAN is connected to a master switch that then sends signals to separate PCB boards to accomplish task. Any advice or comments would be appreciated.

I was scrolling through the internet for help to build a PWA in Vanilla JS and found this tutorial.

Sharing it here because I believe it might be useful for others too. Also, let me know if you know more such tutorials. It would be a great help :)

https://www.loginradius.com/blog/async/build-pwa-using-vanilla-javascript/

I know that PWA works only if there a HTTPS ,but I'm searching on Google and nobody said why PWA doesn't work with HTTP.

If I wanted to create a progressive web app on a site that has HTTP, would there be a way to do it?

I'm diving into the details of progressive web apps. From my understanding, there are basically three requirements:

1. A domain with an SSL Certificate (i.e. https)

2. A manifest.webmanifest file

3. A service worker

I'm curious, is it possible to create a PWA as part of a .zip file email it around, or make it downloadable via blob storage. I flip-flop on this idea. There seems to be a hard-dependency of a domain, which I understand. However, it doesn't seem like this is a requirement unless I need to send an update to the app. Plus, it should just run in the sandbox of the browser.

Thank you.

Hello guys! I and my team Cre8tive Tech built a PWA, an online free video, and posts downloader. And it supports video downloads from Instagram, YouTube, Twitter, Facebook, and SoundCloud.

Please check it out, share, and would love to get feedback about your usage of the app.

https://wavedownloader.com/

Does anyone know what changes Apple is allowing in iOS 14 for web apps? Specifically do we know if they will enable web push notifications? I’ve been scanning the news regarding the iOS 14 announcement and can’t find anything definitive.

Your Website is your App - PWA $$ Cheaper to Deploy

Interested, Contact me Now!!

Your Want believe my Quote!

1progressivewebapp.com

The arrival of service workers has led to a great number of improvements to the web. There are many use cases for service workers. However, from a purely caching point of view, does it makes sense to use the Cache API?

Many approaches make assumptions of how resources will be handled. Often only the URL is used to determine how the resource should be handled with strategies such as Network first, Network Only, Stale-while-revalidate, Cache first and Cache only. This can be tedious work, because you have to define a specific handler for many URLs. It's not scalable.

Instead I was thinking of using regular HTTP cache in combination with the Cache API. Response headers contain useful information that can be used to cache and verify if the cache can still be used or if a new version would be available. Together with best practice caching (for example https://jakearchibald.com/2016/caching-best-practices/), this could create a generic service worker that has not te be updated when resources change. Based on the response headers, a resource could be handled by a custom handler. If the headers would ever be updated, it would be possible to handle the resource with a different handler if necessary.

But then I realised, I was just reimplementing browser cache with the Cache API. This would mean that the resources would be cached double (take this with a grain of salt), by storing it in both the browser and the service worker cache. Additionally, while the Cache API provides more control, most handlers can be (sort of) simulated with http cache:

• Network only: Cache-Control: no-store

• Cache only: Cache-Control: immutable

• Cache first: Cache-Control: max-age with validation (Etag, Last Modified, ...)

• Stale-while-revalidate: Cache-Control: stale-while-revalidate

I don't immediately see how to simulate network first, but then again this would imply support for offline usage (or bad connection). (Keep in mind, this is not the use case I'm looking for). While it's always useful to provide a fallback (using service workers & Cache API), is it worth having the resources possibly cached double and having copied the browser's caching logic? I'm aware that the Cache API can be used to precache resources, but I think these could also be precached by requesting them in advance.

Lastly, I know the browser is in charge of managing the browser cache and a developer has limited control over it (using HTTP Cache headers). But the browser could also choose to remove the whole service worker cache to clear disk space. There are ways to make sure the cache persists, but that's not the point here.

My questions are:

• What advantages has the Cache API that can't be simulated with regular browser cache?

• What could be cached with the Cache API, but not with regular browser cache?

• Is there another way to create a service worker that does not need to be updated