Re: [w3c/ServiceWorker] Soft Update seems way to aggressive (#1250)

> Forcing unnecessary bandwidth

Given HTTP 304, this is a pretty tiny right? Or are you talking about times an update is available?

> and radio power usage

It's likely the radio will wake to fetch data within the app. Or do you think there'll be a high percentage of apps that don't need data at all?

If you're building offline-first, you're already saving a lot of bandwidth/power over a traditional website with the current defaults, and you can opt into further savings if you understand the trade-offs. With `updateViaCache: 'all'` developers were having difficulty getting their service workers to update, since they were stuck in the cache. This is due to servers that set caching headers on JS by default.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/issues/1250#issuecomment-352516639