Audio & Attachments in Offline mode

Hello Tom,

Sorry for the delay in getting back to you. Let me see if I can answer all of these.

I understand that once the user clicks to make the site available on there home screen, it will store some data for offline use.

It stores the entire page with all the content that was loaded for the page offline.

How much data gets stored? Only data on the page they clicked? Or all data for every page of the app?

Just the start page, the offline page and the pages they visited. Not the rest of the pages.

Does media get stored offline? (Such as MP3 audio files and images that are linked as attachments on the page, not as images on the page)

Attachments are not loaded during page load, so they will not be stored offline.

If a user clicks to store a page offline, but then disconnects from internet before download completes, will the download continue once they go online again? or is it stopped?

The service worker handles file by file. If the network is broken mid download of a file, that will not be stored and as of now, will not be resumed when the network comes back.

I feel like you have something specific in mind. What kind of website are you trying to convert into a PWA?

Best regards.

I’m building an audio tour. It would effectively be a 1 page website.

Multiple embedded mp3 audio files on one single page. The “offline Page” would be perfect for this.

But, the concept would only work if when the user adds to homescreen, all the audio files would be cached without them having to click every file first.

Can PWA’s support forced caching embedded elements on a page? Is there a possibility to custom code something that would force that caching? Or is that impossible given the current architecture of PWAs?

If audio files could be cached, how long would they last in cache?

Thanks!