You have:
Content that regularly updates, such as stock tickers, rapidly changing prices or inventory levels, or other real-time data
A chat or comms platform, requiring real-time updates and push notifications for new items coming in
An audience likely to pull data and then browse it offline, such as a news app or a blog publishing many articles a day
A site with regularly updated content which users may check in to several times a day
Users who are mostly using a supported browser
In short, you have something beyond a normal website, with interactive or time-sensitive components, or rapidly released or updated content. A good example is the google weather pwa:
If You’re Running a Normal Site
With a blog that maybe updates every day or two, or even less frequently. Then whilst it might be nice to have a site that acts as a pwa. There’s probably more useful things you can be doing with your time for your business.
How they work
So, you have something that would benefit from this sort of functionality, but need to know how these things work. Welcome to the wonder that is the service worker.
Service workers can be thought of as a proxy that Medicare Insurance Lead sits between your website and the browser. It calls for intercept of things you ask the browser to do, and hijacking of the responses given back. That means we can do things like, for example.
What Service Workers Can Do
Hold a copy of data requested, so when it’s EL Leads asked for again, we can serve it straight back (this is called caching). This means we can fetch data once, then replay it a thousand times without having to fetch it again. Think of it like a musician recording an album — it means they don’t have to play a concert every time you want to listen to their music. Same thing, but with network data.
If you want a more thorough explanation of service workers, check out this moderately technical talk given by jake archibald from google. Service workers fundamentally exist to deliver extra features, which have not been available to browsers until now. These includes things like: Background sync, for updating data while a user isn’t using the page/site
Offline caching, to allow a for an experience where a user still may be able to access some functionality of a site while offline.
