Skip to main content
Inspiring
November 22, 2016
Question

Slides that continually crash on mobile devices...

  • November 22, 2016
  • 1 reply
  • 119 views

I have a software demo project that works well on a PC, but there are several pages that work very poorly. When I jump to one of these pages on an Ipad, the browser typically crashes. 

One of the problem pages is a slide on which I have 11 image-buttons.  (I am using a German Captivate interface, so I am not sure what they are called in English.) These buttons are placed over different fields in the software. (When I say 'software', I mean the software that we recorded when making the project.)  The user can click on any of these buttons and see information about that field.

  Anyway, I have 11 of these customized buttons (made with our own graphics), and when you click on one, its state/status changes to a "clicked" state/status, and all of the other buttons return to a "normal" state/status.  The clicked state/status for each button is the button plus a smartshape with text.

I have several of these type of slides in the project, and if the browser doesnt crash when the user jumps to the slide, it often crashes after the user cicks several, but not all of the buttons.

I have tried to use Dev Tools in Chrome to see what is going on and I noticed the browser simultaneously downloads a large number of very large JSON files on or before the slide, which I assume represent the text fields that are shown when the user clicks or each of the buttons themselves, but I can't be sure. I assume that this could be too much for mobile browsers. 

Does anyone have experience with this problem and/or tips?

- Ryan

This topic has been closed for replies.

1 reply

Lilybiri
Legend
November 22, 2016

Just an idea: why do you not use a shape button, instead of a combination of an image button over a 'field'? That would allow you to add text in the Clicked state, because a shape button can also be functional as a text container, which means that you can change the text in all states. It would avoid to have a multitude of unnecessary objects on slides.

What is the 'field' you are pointing at? I have no problems with understanding German, only with writing (do not like to write with many grammar bugs). How did you set up the actions? Since you cannot change a state of an object on a slide from another slide, I suspect you are using the On Enter action of that slide.