Exploring Use cases of service workers

[Rahul Tiwari]

Hi guys,

We are about to start building a web application which do not have any business requirements for it to be a PWA or offline first.

But while going through service worker working concepts find it really exciting and wanted to explore use cases where SW can be used and could be a value addition to our app.

So we wanted to understand few things about SW :

•  As SW can intercept all the requests going from browser to application server, for that reason can SW implementation also worked as a single entry/exit point for all the requests and response so that we can keep track and log how many requests are sent to server, how many responded and how many are still pending or got stuck because some reasons.Can SW provides than reliability to implement this sort of feature for a large web application.
• So far, there is no debate that it provides better mechanism for caching the static resources and have no issues whatsoever which were faced with appcache, so is it a good idea to use service worker for resource caching and for the feature mentioned in the step one, as having multiple static resources to be cached it could increase the chances of any failure that will result in SW not getting installed/registered and our mechanism we want to rely on SW as in point 1 would get hurt.
• Also it be exciting and helpful to know views on other unexplored cases(other than push notification/supporting offline) where this SW API could be used to help developer to get details about network requests which can make web experience better.
  

Thanks,

Rahul