26 Replies
Christine Hendrickson

Good morning Jon and welcome to E-Learning Heroes!

Our newest product, Articulate Storyline, allows you to publish content to Flash, HTML5, and the Articulate Mobile Player app for iPad. To learn more about Storyline, click here:

http://www.articulate.com/products/storyline-overview.php

To learn more about publishing Storyline content for HTML5 and the iPad app, click here:

http://community.articulate.com/tutorials/products/publishing-a-project-for-ipad-or-html5.aspx

The next version of the Articulate Studio products will also publish to HTML5 and run on iOS devices. Although we can't confirm the release date of future products and upgrades, you can stay informed by subscribing to the Articulate Word of Mouth Blog here:

http://www.articulate.com/blog/


In the meantime, if you want to run your Articulate Studio '09 content on non-Flash supported devices, we're aware of several third-party solutions that may meet your needs. Please be advised, these are not developed or supported by Articulate, so we encourage you to test them out to ensure they meet your needs.   

HTML5 player:

http://frameentered.com/content/low-bandwidth-html-articulate-player-waudio-reports-lms-too

iSWiFTER browser app for iPad:

http://itunes.apple.com/us/app/iswifter/id388857173

Rover browser app for iPad:

http://itunes.apple.com/us/app/rover/id483262612

Screenr:

If your Articulate content does not include interactive elements (such as quizzes or user-initiated navigation), you can record your Articulate content as it plays, using a screencasting tool like Screenr (http://screenr.com), to capture a video of your Articulate content. Screenr is free, and screencasts can be viewed on iPads and iPhones directly from the screenr website. There are also options to publish your Screenr screencasts to YouTube and to download MP4 versions, both of which also play on non-Flash devices.

For more ideas on mobile learning, check out the following Rapid E-Learning Blog post:

http://www.articulate.com/rapid-elearning/m-learning-101-ill-take-my-rapid-e-learning-to-go/

Please let us know if you have any other questions.

Thanks, Jon!

Christine

Rick Cheeseman

Thanks for the links Christine.  I have published a Storyline course for Web, including HTML5.  It has no swf content and runs fine on an HP Touchpad Tablet with webOS 3.0.5.  However, it does not run well on an iPad mini with iOS 6 or Samsung Galaxy Tab 2 7.0 with Android 4.1.1


The problem is with all inserted video files.  On the Tab, the first frame flashes and then the window goes dark.  On the iPad, the first frame stays up for the length of the timeline in Storyline, but neither the video nor audio play.

The videos I inserted were .mov files.  The .mov files were recorded at 25fps, h.264 codec.

There are over a dozen other 'slides' in the course and all seem to work as designed, except for any inserted videos.


Do you have any idea what is wrong?  Thanks, Rick

Christine Hendrickson

Hi there Rick,

First, I'm afraid I won't be able to help with the Android device as we currently don't support those particular devices at the moment (though, once the issue is resolved, perhaps it will work on the device using the unsupported methods I mentioned earlier). 

Have you tested the course on a desktop? I assume so, but never hurts to ask. 

What version of Storyline are you currently running? You can find this information by clicking on "Help" and "About Articulate Storyline". If you're not running version 2 (1212.1412), please download and install Update 2 from the link below. Once you've downloaded an installed the update, try republishing and uploading the course and see if the videos play properly.

Articulate > Download Storyline Update 2

For the iPad, try to make sure you have "Private Browsing" disabled:

Articulate Support > HTML5 output doesn't load correctly in Safari with Private Browsing enabled

If the problem continues, are you able to share the file with our support team for testing? You'll be able to attach the .STORY file on the second page of the following form:

Articulate Support - Submit a Support Case

Please be sure to include a description of your issue. Please also include the URL for this thread in the form. Also, please share the case number with me. You're welcome to do so here, or in a private message. This way I can follow the progress of the case and update this thread.

Thanks, Rick!

Christine

Rick Cheeseman

Hi Christine, thanks for the quick reply. 

As you guessed, it runs well on MacOS and Windows desktops.

The latest I heard is that Android tablets are expected to overtake Apple in 2013 so I can only hope that becoming Android-compatible is at the top of the Storyline to-do list.  I just started with Storyline, purchased last week, and I thought I had done my homework on what Storyline supported.  When the video page said that html5 was supported, I assumed that would include Google for Android on Android OS over 4 (or 4.1, not sure which).  A specific note on that page that Storyline does not work on Android even with Chrome for Android would have been nice.

Just checked and I do have 1212.1412 and Private Browsing was off.  So, I guess I'm off to submit a ticket. 

Thanks much!  (and I will definitely keep you posted on what happens.)

Rick Cheeseman

I'm leaving this record here, for the record.  

I started with Storyline about 6 weeks ago with the express goal of designing a presentation format that would work well on desktops and laptops but was targeted specifically at tablets, all sizes.  I then developed two stories as proof of concept:

1. gaia-tree.ca/nae1/story.html

2. gaia-tree.ca/wtg/story.html

The first is a multi-scene story that incorporates videos.  The videos in the 2nd and 3rd scenes are the entire stage.  In later scenes, the videos are one component on the stage.  All videos in the first story began life as .swf files which I screen-recorded to .mov files using H.264 and 25fps.  I inserted the .mov files (not the swf files) into Storyline with no trouble.

The second story is a one-scene test of a number of design elements that weren't used in the first story, the primary one being a DVD source from which I screen captured a small segment.  The screen capture was done with the same app as the videos in the first story and the recording was also done with H.264 and 25fps, and the output was also a .mov file.  Again, the .mov file inserted easily into Storyline.

Both stories were published for WEB with HTML5, and not Articulate Mobile Player (I did not want the human to have to download an app).

Testing was done by Articulate Support (hereafter AS) and me.  Here are the results of all tests:

A) Both stories ran as designed on:
• Mac OS X 10.6.8 and 10.8; Safari, Chrome, Firefox
• Windows XP and 7; IE
• HP Touchpad Tablet with webOS 3.0.5; Chrome
I did all these tests.
 
B) On both Android and iOS, the native Storyline components ran as designed but there were numerous problems with the videos.   Complicating things is the fact that AS and I observed different results even with the same OS.

C) iOS (Private Browsing off, Javascript on); Safari
• me: iPad mini MD993C/A, iOS 6.1.2 - Videos in first story didn't work; video in second story did work
• me: iPad MD911C/A, iOS 6.1.3 - Videos in first story worked sometimes and sometimes not; video in second story worked
• AS: iPad?, iOS6.1.2 - The first video in the first story worked; other videos in the first story were not tested
• AS: iPad2, iOS6.1.3 - The second story worked; Videos in the first story were not tested

D) Android, native browser
• me: Galaxy Tab 2 7.0, 4.1.1: no videos in either story worked
• me: Galaxy Note 10.1, 4.0.4: all videos in both stories worked
• AS: tablet unknown, 4.0.2: first video in first story worked; other videos in first story not tested; video in second story worked.

E) Android, Chrome
• me and AS: Chrome didn't do well on any Android OS

Conclusions:

1.  Storyline may work flawlessly with iOS in conjunction with the Articulate Mobile Player but it is inconsistent with HTML5 only.  In future, I will publish with AMP selected.  At this point, I can only assume that everything will work when AMP is installed (and you know what they say about assumptions).

2. Android 4.1.1 is ; Chrome on Android is of similar ilk.

3.  Of the OSs that don't support swf, Android 4.0.x appears to be the best HTML5 performer, despite the fact that Storyline does not officially support Android.

Opinion
The fact that Articulate does not specify on any Storyline tech spec page I could find that Android is not supported does not reflect well on the product or the company.

Future
There has been a great deal of talk over the past year, and more, about the need to develop courseware for tablets.  Based on that I assumed that there must be many who have tried to develop courseware for tablets using Storyline, and so I was going down a well worn road.   That assumption appears to be wrong since the problems I have run into do not seem to be well-documented already (as I believe they would have been if many were developing for tablets), or everyone is developing for iPad only.  If any readers actually got this far in this 'record for the record', and can enlighten me as to what is actually happening in the courseware-for-tablet world, I would appreciate it.

Thanks,

Rick

Rick Cheeseman

Thanks Steve, that is more definitive, but, in the case of HTML5, I would disagree that 'iOS 5.0 or later' is supported as my testing of 6.whatever wasn't consistent.  I haven't tested iOS + AMP but I am hoping/praying that everything will work as designed with that configuration.

In any case, the real issue is creating eLearning for tablets.  Based on the response to my report and other investigations I have been doing since, it appears that 'tablet' and 'iPad' are used synonymously by many, including many who want their eLearning to be available on desktops and tablets, one solution for all.  I think it is fair to predict that, with Android already head-to-head with iOS, 'tablet' and 'iPad' are not going to be synonymous much longer.  When that happens, we can be ready, or not.  Right now, Storyline is not.

Nigel Ribeiro

Just read this article which says that Android has overtaken Apple as the top selling operating system. Quite a few of my clients have been asking about android support recently.  Would be great if Articulate could develop a andriod app.  

http://gigaom.com/2013/05/01/ipad-is-top-selling-tablet-but-android-now-most-common-tablet-os-says-idc/

Leslie McKerchie

Hi John and welcome to E-Learning Heroes!

Articulate content may work on some Android devices, but we don't currently support them. We can't make any promises, but we care very much about supporting the operating systems and devices our customers are using. We're listening to your feedback and taking it seriously.

If you would like to submit this in the form of a feature request, you can do so here.

Neil Hoskins

Rick, I've been having a very similar experience, and agree with your findings and opinions 100%.  And it's now several months after you posted them.  There is a tutorial on this site somewhere (can't find it right now) that claims it was last updated 60 days ago, stating that, "most Android devices run Flash", which is clearly bunk.

My client is adamant that she wants standalone/offline eLearning for tablets and I completely agree with her reasons for wanting this.  What I have found so far is that Adobe Captivate has a rather kludgy-but-it-works way of developing installable apps for Android and iOS using PhoneGap Build, but you then have the problem of getting the app onto the tablet, since we don't want the app to be available in the public app stores.  Android will allow apps to be installed from other sources but getting apps onto selected iPads would involve jailbreaking, which is a non-starter.

The approach taken by Articulate Storyline on iOS seems far more elegant: you download a client from the app store for your iPad which will download the HTML5 eLearning and make it available offline.  Perfect, except it's not available for half the tablets on the planet.  At the moment, it's looking like we're going to have to develop the eLearning in Captivate, and then port it to Articulate Storyline for the iOS version.  If only there was an Android equivalent of the Articulate iOS client, we could do the whole think with Articulate, or if there was some way of getting an iOS app onto an iPad without going through the app store, we could do the whole thing with Captivate.

Rick Cheeseman

I feel your pain Neil.  I am hopeful that now that the new version of Articulate Studio is out, more resources will be available to develop an Android app.  Unhopefully, it is probably just as likely that supporting the new Studio will suck up all those resources. 

I am beginning to wonder if the reason for the delay in an Android app is that the number of people REALLY designing for tablets is small.  To this point, all my Storyline development is self-directed, for free, so I've been able to put ongoing effort on hold, hoping for an Android app.

If you are interested, I think I have developed a presentation size and orientation that works on everything from 27" monitors to smart phones: gaia-tree.ca/nae1/story.html 

Cheers!

Neil Hoskins

You're probably right about tablets and limited numbers, but it's a classic chicken-end-egg: maybe more people would develop eLearning for tablets if it wasn't so painful.  Anyway, we're going the Captivate route now:  we'll use PhoneGap Build to package both Android and iOS apps, and it turns out that you can make iOS app store apps available to only certain people.  Sorted.

Caelyn Nagle

I can't believe that it's 2014 now and there STILL isn't an Articulate Player App for Android. I have yet to find an Android device that plays Presenter 2013 content properly., phone or tablet. The fact that they keep saying that they don't support "those devices) is interesting. Just because Apple's Devices are almost synonymous with their iOS doesn't mean other devices are synonymous with their operating systems. I would think that if they make an APP for Android OS, that it should work on most Android devices (with a few outliers of course for cheaper Android phones and tablets)

It really bugs me how it seems nearly everyone in Education seems to think that Apple is the only maker of mobile devices. They've fallen for Apple marketing hook line and sinker. (Not that I hate Apple products, I have Apple devices myself) Those of us in the technical support areas of Universities know better, students definitely know better. Articulate should know better.

Ashley Terwilliger-Pollard

Hi Caelyn,

I certainly understand the desire and need for support for Android devices, and it's something our Development team is also aware of. The general issues with offering support for Android lies in the HTML5 output. It's important to keep in mind that the HTML5 standard is not yet finalized (and that a stable HTML5 recommendation is not scheduled for release until the end of 2014), so HTML5 is truly a "bleeding edge" technology at this time.

While the Articulate products do an excellent job of producing HTML5 content, unfortunately most Internet browsers have not fully adopted the HTML5 standard yet.  For an excellent overview of the state of HTML5 adoption in modern browsers, I recommend taking a look at html5test.com.

For these same reasons, we recommend the use of the Mobile player app while on the iPad and if needing HTML5 output to view it from within mobile Safari.  If you'd like to see additional support for other browsers and operating systems I'd recommend sharing your thoughts in the form of a feature request as those are received by our Development team. 

Laura Winzen

The Android browsers may not run the HTML5 code correctly yet but they should darn well be running the Flash code right after all these years! The problem I am having is that the player which fits the screen perfectly on an ipad, pc, iphone, or mac gets cut off on an Android device. The user has to scroll down on every slide to find the Next button to advance the education. I'm incredulous that the Flash isn't working correctly to size the player display. Do I misunderstand how this works? If Android is screwing up because it is trying to use the HTML5 instead of the Flash code, is there a way I can force it to use Flash on these devices? 

Laura Winzen

Ok, so Articulate doesn't support Android but maybe the community has a response. I have created a piece of education in Storyline and this is how it displays on iPad and how it displays on Android. As you can see, the player is sized perfectly in the iPad window while the bottom of the player is cut off on Android.

Even worse, as soon as I touch the Android version to scroll down to see the player controls, the page goes blank and nothing works. Has anyone been able to resolve these Android issues?

iPad display...

Android ASUS tablet display...

Lars Eversmann

Hi,

I try to open our Elearning Course with android Phone or Tablet. But it doesn't work.

For example, I have upload a published web course on a android phone. I have uploaded it on document. Then I open this file. When would like open the file with story.html or story_5.html. I see only html viewver. I can open the file with my browser.

How can I proceed ?

Thanks

Emilie

Scott McLeod

I've had some luck getting the standard Android browser on a Nexus 7 (Running CyanogenMod) to read the Articulate presentations properly.

I've got an HP TouchPad running CyanogenMod Android for TouchPad that will play the presentations, but with no audio.


No Android phone that I've tried yet has successfully played a presentation. (either SWF or HTML5)

The Photon browser has also had some luck playing presentations, but the drag & drop interactions don't work, and the audio is hit or miss.

Has everyone in this thread submitted their feature request for a native Android player (for both tablet AND phones) yet? If not, please go submit that request right now so Articulate can allocate the required developers to get this done. From what I've been seeing across the forums here, it's a priority on just about everyone's plate, it needs to get done ASAP. The only way they can justify allocating developers (it seems) is if enough people submit feature requests...

I'd be interested in getting in contact with other E-learning devs that are testing w/ android though to see if we can figure out a workaround in the meantime.