Reliance on SCORM Dependence on Java
Today we are continuing our series on what is holding back large-scale mLearning deployment. Before we begin this discussion, we need to address those of you who are up on the current happenings surrounding SCORM. Some of you are aware of Project Tin Can and how it represents the “next-generation eLearning specification” (http://scorm.com/tincanoverview/) and will provide the means for tracking mLearning content. While not explicitly stated, this has apparently come to be regarded as a replacement for the SCORM model, which begs the question, what happens to SCORM 1.2 and 2004 if Tin Can is implemented? Intriguing thought, but probably not for this post.
Tin Can represents a way to track mobile learning, but it takes a long time to go from a specification to large-scale adoption, which isn’t ideal since our customers are searching for something they can do today. Swept up by the rise of iPads and smart devices, the pressure is on providing a migration path, enabling immediate online access to the content.
While there is a lot of discussion about “real” mobile learning, our customers are frantically searching for ways to provide mobile access to content stored in their LMS’s. As LMS’s enable mobile login capabilities, the question quickly turns to “Why can’t I launch the course from my iPad?”
Great question. Why can’t they launch the course, and why does the current SCORM model prevent mobile access? Let’s take a look.
The main reason the course can’t be successfully launched via a mobile device is because every LMS we have ever worked with (e.g. Plateau, Saba, SumTotal, etc.) launches a SCORM course using a Java Applet, requiring the client to install Java. Unfortunately, most mobile devices (especially iPads and iPhones) don’t support Java. Game over.
Why is this holding back mobile learning overall?
First, many eLearning developers and customers rely on content being delivered as a SCORM package; so naturally, many authoring tools publish SCORM packages to load their content into the LMS. As a result, providing mobile access can be a difficult task for both tool vendors and custom eLearning developers.
Somewhat ironically, because of this industry-wide standard, mLearning’s growth has been severely hindered, as organizations can’t simply flip a switch to enable mobile access to the content.
The second major issue is lack of education. This shows up in numerous conversations where a customer requests that a) all their content be published as a SCORM package, and b) that it is accessible using mobile devices. The conversation about Java supportability quickly follows!
What’s the solution? The most effective way to address this issue is to bundle SCORM, AICC, Flash, and HTML5 into a cohesive package. Publishing “for mobile” or “for desktop” is fine, but most customers we deal with need both and having to manage two courses in the LMS opens a new can of worms. As implied, we must figure out how to best render the course (e.g. Flash for some users, HTML5 for others) for a given user on their device. By bridging both worlds (desktop/SCORM with mobile) organizations can move ahead and fully embrace mobile…today.
About CourseAvenueVisit us at www.CourseAvenue.com
- Just registered HighConsequence.Training (#Training, #learning ) - More (much more) to follow. - 6 days ago
- 2012 in Review: The Top 8 Topics in the eLearning World wp.me/pzgsk-bT - 2 months ago
- Temporary System Interruption wp.me/pzgsk-kN - 8 months ago
- Temporary System Interruption wp.me/pzgsk-kK - 8 months ago
- Temporary System Interruption wp.me/pzgsk-kF - 8 months ago