What is better to make an offline application cache or a web application production service?
I want to make my web application available even if the network is not installed or the user is not connected to the network.
I searched about this and found two solutions: 1) use the app cache 2) use the Servant
As a service worker, it is under development and not supported by all browsers, so cannot find what is possible according to my requirements.
On the other hand, the application cache is almost outdated (MDN site) from most of the browser (still supported in many browsers), I can't go with this solution either.
Please give some suggestion or correct me if I am wrong in the above points.
Thanks in advance.
source to share
Your statement is correct. The support staff are not supported by all browsers at this time, and I don't think Safari will support it in the near future, but at least it appears on the five year plan .
You can still use the app cache even if it doesn't have all the sw functionality and even if it is deprecated. Your site may have a sw / application mixed mixer.
You need to compare the benefits to the work / money you want to put on your site to make it work offline. If you have an existing site, you can check your browser statistics and then make a decision.
source to share