You might not need a service worker(jayfreestone.com)
jayfreestone.com
You might not need a service worker
https://www.jayfreestone.com/writing/you-might-not-need-a-service-worker/
6 comments
While working on a small atproto OAuth client I discovered a neat service worker pattern that I don't think I've ever seen someone write about. The page makes normal fetch requests, and the service worker adds the authorization header and handles token refreshes/dpop retries/etc under the hood. https://tangled.org/jakelazaroff.com/atsw
> I’d argue that this is more of a question of ‘do I need offline support?’ For Slack, sure, but for many apps, probably not.
I like offline support. I enjoy it when an app I use supports it. And I want to add support for it in my own app. But, it is a hard problem. And to the best of my knowledge there is no framework or library that that solves the hard problems for you.
I like offline support. I enjoy it when an app I use supports it. And I want to add support for it in my own app. But, it is a hard problem. And to the best of my knowledge there is no framework or library that that solves the hard problems for you.
I can appreciate the author's perspective, but in my experience the magic of bringing the online world offline gave our product (https://ww.cardcluster.com/install - duelists, give it a try!) a significant amount of stickiness compared to other similar services. But it should be noted that we built our product with service workers in mind from the beginning; trying to retrofit service workers into a mature application with paying customers and all sounds extremely tricky.
I got a dns not resolved error.
https://cardcluster.com/install - I gotta check my links better!
the offline mode is literally offline :p