@slightlylate @wanderview how often do Chrome and FF Soft Update SWs? I’d like to pre-cache newly deployed assets before next navigate.
-
-
Replying to @ericf
@ericf@slightlylate@wanderview I guess they follow generic caching rules & headers.1 reply 0 retweets 0 likes -
Replying to @RReverser
@ericf SoftUpdate runs after every navigate FetchEvent and after other events if 24 hours since update. /@RReverser@slightlylate2 replies 0 retweets 2 likes -
Replying to @wanderview
@wanderview@RReverser@slightlylate So no way to cache new assets _before_ a user navigates to the app after a new version was deployed?1 reply 0 retweets 0 likes -
Replying to @ericf
@wanderview@RReverser@slightlylate …until Background Sync or UI-less Push?1 reply 0 retweets 0 likes -
Replying to @ericf
@ericf Right, background-sync is what you want for that. Using push to sync resources is an anti-pattern I think. /@RReverser@slightlylate3 replies 0 retweets 2 likes -
Replying to @wanderview
@wanderview@RReverser@slightlylate is SW reg in <head> advised with early flush to pre-cache while server renders <body>?2 replies 0 retweets 0 likes -
Replying to @ericf
@ericf@wanderview@RReverser: for the next 6-12 months I think state of the art will be sync on push notification & startup1 reply 0 retweets 0 likes -
Replying to @slightlylate
@slightlylate@wanderview@RReverser I want bookmark clicks and start pages to load fast for a continuously deployed app.6 replies 0 retweets 0 likes
@ericf @wanderview @RReverser: SWs/PWAs put you in a world that's a hybrid of web and native app architecture.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.