The best approach today for stand-alone web applications

Question

I am trying to create a web application that needs to work offline from time to time. The standard approach so far has been to use the browser application cache. However, it looks like the application cache is outdated and will be removed from browsers in the future (see https://developer.mozilla.org/en-US/docs/Web/HTML/Using_the_application_cache ). The recommendation is to use the Employees. However, Service Workers is currently not fully supported in all browsers.

So what to do? What is the best way to create a stand-alone web application today, given the current state of the application cache and production services? Are there other approaches that are less dependent on browser features?

Answer 1

You can use service workers and AppCache in the same web application. What happens in this case is that browsers that do not support Service Workers will use AppCache, and those who do this will ignore AppCache and let Service Worker get the upper hand.

Source: https://developer.mozilla.org/en-US/docs/Web/API/Service_Worker_API#compat-mobile

Chrome problem: https://crbug.com/410665

Personally, I would not worry about AppCache if offline is not the main part of the application.