I'd recommend sending feedback to the support team through the in-app feedback – I agree that it would be nice to have offline images (especially in image-based collections, like New Testament Stories or the Gospel Art Book).
In case you're curious, there are technical reasons why Gospel Library doesn't download images with the content. Content doesn't actually include images – instead, it includes URLs that tell Android (or iOS) where to get the images. To explain:
The HTML code (Gospel Library "content") for a map page might look like this (simplified representation):
Code:
<html>
<body>
<h1>1. Physical Map of the Holy Land</h1>
<p>This is a paragraph.</p>
<img src="https://broadcast.lds.org/crowdsource/mobile/images/1506024/b5745a2fb4be41449b0b7de654f0118b/2231x3247.png" alt="Bible map 1" />
</body>
</html>
In order to make the images available offline, Gospel Library would need to:
- Search through each HTML content page that has been downloaded.
- Get the URL for each image.
- Download the image and store it with app data.
- Modify the content so that it points to the local image instead of the broadcast.lds.org URL.
- Save the original URL for the image somewhere so that if images get cleared or corrupted somehow they can be downloaded again.
Then, of course, there are questions like: What if the user isn't connected to a good internet collection for downloading images (which can be large), when they first download the content? Do users want all of the images in any content they download to take up space on their device? What about users who, by habit, download all of the content (magazines back to 1971, etc.)? It would be difficult to set different rules for different books, and all of those images add up.
