Skip to main content
M
markclaxton_
Inspiring
October 11, 2016
Question

Projects crashing on iPad and other mobile devices...

  • October 11, 2016
  • 1 reply
  • 389 views

Hi!

For a client we created 3 eLearning projects in Adobe Captivate 9, everything works smoothly on desktop browsers, but on iPads and other tablets and mobile devices it crashes the browser, whether it's Safari or Chrome etc.

Could the size of the project be at fault? The size of each project ranges from 45mb to 80mb.

This topic has been closed for replies.

1 reply

eLearning Guy
eLearning Guy
Inspiring
October 11, 2016

That project size shouldn't be an issue. Without knowing more about your project, one thing I have found that can cause freezing of projects on mobile, especially older/slower mobile devices, is trying to output two sound channels simultaneously. The primary example of this is having audio narration playing and also having the mouse click sound enabled. 

But really, you will need to provide more information for anyone to realistically help. For starters:

  • When does the crash occur? (at startup, on a specific slide, after a specific action, etc.)
  • Does it crash exactly the same way/cause for all courses?
RodWard
Community Expert
RodWardCommunity Expert
Community Expert
October 12, 2016

If an HTML5 project is crashing the browser on a tablet it's highly possible that playback of the project is requiring more resources than the tablet OS can allocate at some point.  When this happens, the mobile OS will seek to protect itself by closing down whichever app it believes to be the resource hog.  In this case it will be the browser playing the e-learning module.

RAM memory is usually still quite limited on mobile devices.  There are some free apps that you can download and install which will show you the current system resource usage of your device at any given time.  Using these apps, you can simply watch what is happening as you play the content.  If the issue IS resources running out, you should see the indicators slowly climb until the OS kills it.  If the issue is something else entirely (e.g. crashing due to some coding bug or conflict) your resources should look fine at the point the crash occurs.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices