Anyone familiar with Vablet and potential issues running Storyline content?
Mar 25, 2015
Hi all,
We've developed some elearning modules in Storyline 2 and have had reports of performance issues from end users who are viewing them through something called Vablet on their mobile devices.
At this stage I don't have an awful lot more detail than this and am reaching out to the community as well as investigating further with our client, if I find out any further info that may be relevant I will update accordingly.
In the meantime, has anyone viewed any Storyline content through Vablet and if so have you experienced terribly slow load times and significant lag when navigating between slides?
As far as content goes, we've published images at 100% quality and there are no videos or audio so everything should be fairly light, average filesize when published is ~10MB.
EDIT: The device has been confirmed as iPad2.
Thanks in advance.
7 Replies
Hi David,
Taking a look at this Vablet App, i can say it is not something we support for viewing content on mobile devices. You can check out the system requirements for iPads here.
Hopefully if others in the community have used this they may jump in with some assistance.
Hi Emily,
Thanks for replying to my post. I figured Vablet wouldn't be supported, to be honest until yesterday I hadn't heard of it as it has been sprung upon us way down the line in terms of development and deployment of content.
In terms of improving performance on the iPad in general we've resolved to remove slide/layer transitions which seems to provide a visible improvement when navigating through our modules, some of the lag could definitely be attributed to the transitions.
Thanks for the update David.
I had not heard of Vablet either. Glad you got things to improve on the iPads a bit, Are you using Mobile Safari or the Mobile App? (for people not trying Vablet) Typically mobile safari does have a few performance issues.
Unfortunately we're unable to use the mobile player for this client so we're left with mobile safari.
I wanted to provide a belated update here. It turns out that the client was trying to run the SCORM files through a non-SCORM environment which was causing the issues. We've since provided HTML5 versions and they are happy with the result.
One other thing that contributed to the seemingly slow load times was that we'd used transparent PNGs to create custom navigation buttons. The problem was that in the HTML5 versions (vs Flash) the areas of transparency weren't included in the button hit area. This led to the buttons sometimes working, when a user hit a solid area, but not when they hit a transparent area. As a result the user felt as though they were experiencing lag when in fact on subsequent attempts to navigate they were actually hitting an area of the button that was solid.
I hope this makes sense!
Thanks for sharing your update David!
No worries, thanks for your help.
This discussion is closed. You can start a new discussion or contact Articulate Support.