I was asking to build an app for a customer, it is basically a restaurant guide he owns and run on the web that he want to be available on mobile phone with some peculiar characteristics (like ‘save to favorites’, ‘navigate to restaurant’ ‘reastaurants around me’ and so on); the guide is really small, they are about 120 restaurants with data like name, map address, description, main image, gallery of images, region and so on, every document can be accessed via API, average size of every document is about 30K not considering the attachments. The app will also support a news section still coming from API
Due to the fact that restaurants documents won’t change often during time and sometimes the API is really slow, i was thinking to download all the restaurant data (except images) at first startup of app, and maybe expose an API method to check if data need to be refreshed. This way the app is available offline (News will be online only, but its irrelevant), even if without images, and API latency is avoided.
I was wondering if this could be a good approach (download about 4Mb of data on startup and store on the user phone) or maybe it’s better a full online experience, or a in-between solution like storing the data on the phone (including photos) first time a document is accessed (and have his cache expire after a X time)
Any suggestion will be appreciated