Welcome to the in5 Answer Exchange! This a place to get answers about in5 (InDesign to HTML5) and make requests.
0 votes
Hi everyone,

I have a 48-page mobile project with lots of galleries, videos, MSOs, etc.

Everything runs smoothly locally and in my desktop browsers. However, as soon as I open the page from the server on my iPhone, I get a message saying that a problem has occurred repeatedly and the page won't load. I've already exported parts of the document, and it worked, but never the entire document. Could it have something to do with Safari's limited memory and too many MSOs? If so, how can I get the problem under control?

Thanks very much for a tip.

FaBi

PS: My coding skills are still limited. :(
ago in bugs by (140 points)
edited ago by
  

1 Answer

0 votes

Hi FaBi, 

Yes, it's very likely that you're getting a memory error on iOS, especially with the videos and a document that is fairly long.

I would recommend using the following tips to optimize your content:

  • Here's an article with tips for improving loading time (and exporting time while you're working on the document) for long documents which are generally greater than 60 pages but can be helpful for any document:
  • Image optimization is helpful too. It's included in the tips in the article above. If you have a Gold subscription, then you can use the Enhanced image optimization which further optimizes images and removes duplicates.
  • You can check to make sure that your images use an appropriate online resolution of 72 ppi for standard or 144 for high definition image quality. Here's more information on image quality that might help:
  • For placed videos, make sure that they are edited down to the dimensions that you plan to use when placing them in your layout:
  • Or you could use a streaming service like YouTube or Vimeo and embed the video
  • There are also some features that increase file size, so you might consider changing some of those options:
    • Larger impact settings:
      • Liquid Layout exports higher resolution images so that they can be scaled up in the browser (as needed).
      • Rendering text as SVG exports a lot more data (vector points for all of the text characters)
      • Embedding local fonts can increase the size, especially with large fonts or large numbers of fonts
      • Increasing the Image Quality can make a large difference
    • More minor differences:
      • Different Page Formats/Features (e.g. swipe) can account for minor size difference because they require different CSS and JavaScript libraries
      • Multimedia will add file size, not just the media but also the libraries
      • Folio Overlays, Social Sharing, and Analytics may require slightly more JavaScript in the output
    • When you export, some files may remain from previous exports (which is why your size may not shrink back down). To remove the unnecessary previous files, make sure the Clear Previously Exported Files option is selected.
      • From the Help doc:
        • The Clear Previously Exported Files option deletes any existing files within the assets directory of the Destination Folder. Using this option ensures that if the export has been run multiple times, unused files are discarded in order to save file space when the files are uploaded to a web server or packaged as an app.
ago by (30.5k points)
Hi Myra,

thank you very much for the detailed help. It really does seem to be overkill for the mobile browser. The interesting thing is, as soon as I remove the burger menu (10 chapters as bookmarks accessed via buttons), things seem to work better. I then created the chapters with hyperlinks, but unfortunately, that didn't provide the necessary savings.

I'll continue testing. There probably aren't any other options for reducing the DOM or memory usage in general, right?

Best regards

FaBi

The approaches that I mentioned above, especially the ones from the Tips article, would be the best options for optimizing your file and consequently reducing the memory required on iOS.

Alright. Thank you very much.