Progressive Web Apps Part 4: Variable Connectivity
One reason to prefer building a native mobile App over a progressive web App, has historically been that a mobile App can work (to some extent) without an Internet connection, using cached data. Whereas, websites can only work whilst an Internet connection is present. However, Service Workers have allowed for web Apps to compete with mobile Apps, providing a solution to accessing certain web pages when off-line.
What is a Progressive Web App Service Worker?
Another benefit of a Service Worker is that they allow for more advanced platform integration, including the delivery of push notifications and allowing for background synchronisation within a PWA.
The amount of caching time can vary for different types of data. This isn’t a panacea to cure all your connectivity problems. Specific programming will still be frequently required to deal with situations where out of data cannot be used. This may include issue warnings to the user, locking out specific functions until connectivity is restored and other novel solutions.
Service Workers allow progressive web Apps to work with varying levels of connectivity. However, it’s worth remembering that the level of poor connectivity that an individual App will tolerate depends entirely on the function of the App.
For example, an App that requires up-to-the-second stock prices will be pretty useless without a reliable Internet connection, whereas a stock price trend-reporting tool might be able to work with data that is hours old.
If you are interested in having McKenna Consultants develop your progressive web App, then please fill out the content form below. If you missed the other parts in our progressive web app series, then head back to our first blog, where we discuss installable web Apps. Or, alternatively, you can check out our case studies, to see the previous work we have done for our clients and understand the wealth of experience we have developing progressive web Apps.