Hi,
I am currently writing an app for the NZ plant network, it is relatively simple app where users can look up information about plants in NZ. The app is very image heavy and will include over 4000 images, even though these images are small in size, the share number of them adds up to over 200MB. These images will occasionally be updated during the life of the app and can be pulled dynamically from their server.
My question is - should I include these images in the final build or distribute a ‘bare bones’ app that pulls down the images when it first loads. I would prefer to include the images in the final build (have the app store or market deal with the large download) and then users would only need to pull down updates (which wont occur that often) but I am not sure how this would work exactly. If I include the images in the final build then they would be located in the ‘resource directory’ and therefore un-editable (I think), if I download newer images (which will replace the old) then I the app will get larger and larger.
Any advice or suggestions greatly appreciated.
Craig