0
Under review

Page turn delay

Laura Stout fa 7 anys updated by Alin Alexandru Matei fa 7 anys 5
I am experiencing delays when moving between pages in my book (this happens both when I click a button I've set up to move to next page, and when I set up an action to jump to another page).
In Interact Builder-Interact mode the delay is about 1 second.
In Interact Player the delay is about 2 seconds.
Is this something that will improve once the app is published to the iTunes Store or Android market? The kids testing my app are frustrated with these delays and are losing interest.
Other (non-Interact Builder) kids apps that I use respond pretty much instantaneously. I also looked at the "About Airports" app built with Interact Builder, and the pages take about .5 seconds with a curl effect.
My book is 27 pages, fairly simple animations, 46 MB.

Answer

Answer
Under review
Could you send us a copy of the app at ezra@interactstudios.com so we can see what the problem is? Thank you for your feedback.
Answer
Under review
Could you send us a copy of the app at ezra@interactstudios.com so we can see what the problem is? Thank you for your feedback.
Thanks Alin...I hightailed a copy of this app to Ezra's email.
Wondering if anyone has had a chance to look at the app I sent?
Thanks
Laura for this situation let us try something: Go to the App properties Click the Cache size and try to clear the cache as shown in the image bellow:

Let us know if this solve the delay situation.
Hi Alin,
Clearing the cache didn't solve the delay.
For page turns, it still takes 1 full second in Interact Mode, and 2 full seconds in InteractPlayer on iPad.
How quickly should I expect my pages to turn? The speed I have now is unsatisfactory.
Thanks, Laura
To help the user understand that their interaction has registered, you could give some visual cue. Many apps make a button glow once it has been tapped, so when the user is waiting for the button to actually work they don't have to doubt that they have in fact tapped the button. As another example, if the graphic element for going to a specific page looks like a button, the element can hide to reveal a different element that looks like the button has been pressed down.