Problem with viewing project on Mobile / iPad

May 30, 2013

Hello. I have a problem with viewing my projects on mobile phones and iPads.
I export the projects including html5 output and also articulate mobile player, I upload the projects on my lms but when I try to play the project from mobile phone or iPad I got many issues. The project has too large resolution which is almost impossible to scroll down to find the next / previous buttons. Alsom the audio file is stopping after the first slide is played.

When I play it on iPad, there is no voice (I don't have articulate mobile player), and again the presentation is too big for the screen, the right side of the project is outside the screen area..

my browser settings are like these:

So, I want to know is there a solution for this problem, if you heard something about this, or?

Also, I need to know is there a way to play a project on iPad without installing articulate mobile player? Because Im sure that the target group for this project will be kinda lazy to download the app, and this will be maybe the first time they will need to download it.

Thank you very much, I would appreciate any kind of help or sharing similar experiences.
Marko

12 Replies
Dennis Hall

Hi Marko:

If you project is a elearning project and you want to present eLearning online, then have the learning go into the field and interact with the project on a mobile device, you should consider creating a project specifically for mobile.

In my experience, I have found that mLearning and eLearning are best kept as separate projects. Once you do this, you will see they can be used together to create a better learner experience.

Simply publishing eLearning to be used on a small screen format Smartphones can be unrealistic due to screen dimensions, multimedia limitations (mobile device only allow one multimedia source to work at a time - i.e. audio or video - not both), and learner cognitive responses (learner overload).

Finally, is your LMS using TinCan communications, if not, you may not get updated data from a mobile device that was used offline.

When developing for mobile, it is really best to consider all these factors.

For the iPad player, this issue of scrolling is due to the project dimensions.

Best Regards,

Dennis Hall

Marko Stojkovski

Hmmm, changing the resolution may fix that problem, but what about the audio part, how can I fix that?
Also, what do you suggest is the optimal dimension for mobile phones and iPads?

And another question, since I have never worked this (editing projects to fit for mobiles / iPads), can someone send me links or explain me the differences between regular creating and creating project for mobile phone?

Thanks.

Dennis Hall

Hi Marko:

To fix the audio, you need to make sure you do not have an audio layer at the same time as a video layer.

If you need audio and video simultaneously, I recommend using a video editor like Camtasia so you only have 1 multimedia item being used at a time.

Here is a list of mobile device resolutions (once clicked, scroll down to see the list) then pick the most common one for tablets and/or phones.

http://en.wikipedia.org/wiki/List_of_displays_by_pixel_density

Hope this helps.

Best Regards,

Dennis Hall

Dennis Hall

Hi Marko:

The object would be to format the projects to those most common resolutions. You for example:

If you pick the most common mobile devices in your target audience, you may find many users use the BlackBerry playbook at 1024×600, while another most common device may be the iPad at 1024×768.

In the examples, I would develop for the 2 resolutions and in each case reduce the project size by 30 pixels in height and width. This will allow for the player surround. With these dimensions, you will also find that when you publish for computer and HTML5, you can set the project to display full screen and everything should work out perfectly.

If you want to also target smartphones (my recommendation is redesign in this case) your display real-estate is much smaller and reformatted, therefore you should find the most common settings for your target audience again and publish once for that setting.

I hope this helps.

Best Regards,

Dennis Hall

Jennie Lee-Pace

I am having all the same issues.  If I understand you correctly, the solution is to publish a course for mobile devices and a course for desktop.  That's two different courses being imported into the LMS.  Correct?   If so, that's two different courses I need to manage and register student's in.  And how will i know which device they will use to view the course?  In an age of responsive design and advance web tools, how is it that we can't create and publish a single course that renders properly across all devices?  

 

Leslie McKerchie

Hello Jennie!

This thread is quite dated and our mobile/HTML5 delivery has become much better.

You mention that you have some of the same issues mentioned here and I'd love to be able to assist.

We have some great documentation here on publishing for mobile devices as well as an article about how Storyline determines what version to display. This addresses some of the concerns you mentioned above. 

  • What version of Storyline are you using?
  • Would you be able to share your .story file so that we could understand what you are seeing?
Jennie Lee-Pace

I wish I had found this forum this morning. I deleted the AS2 test files. In that time I also downloaded a free trial of Storyline 360, so if I open the native AS2 file, it defaults to opening in Storyline 360.

Regards,

Jennie Lee-Pace | Marketing & Sales Manager | AlcoPro
T 800.227.9890 O 865.525.4900 F 865.525.4935
[chat-button-email]

Leslie McKerchie

Hi Jennie - Did you open that file within Storyline 360? If so, it probably upgraded to the new format. A backup file should have been created though. 

Sounds like you now have SL2 and SL360 on the same machine now? That's totally fine of course, just can cause the issue with opening as you've mentioned. 

I'd advise to first open Storyline 2, then Open, and navigate to the correct file to open if needed.

If you are looking to compare versions/features, I'd advise to take a peek at this comparison chart.

This discussion is closed. You can start a new discussion or contact Articulate Support.