There are several technical challenges associated with deploying SCORM content because the current technologies used in SCORM are based on HTTP and JavaScript, which have limited support on mid-end mobile devices. The good news is there are other technical approaches that don't use HTTP and JavaScript that you could leverage as an alternative.
Participants in this session will learn the issues related to deploying SCORM content on mobile devices. Many people are looking for a more lightweight mobile-friendly version of SCORM that can be deployed on mobile devices. This session will look at existing technologies that can be leveraged as alternatives, rather than waiting for SCORM to be updated. You’ll see several example use cases of SCORM implementations and hear the lessons learned from ADL.
4. What I’ll Cover…
• Mobile SCORM Implementations
– Updates on use cases from last year
– New Use Case
– New Solutions
• Mobile SCORM Options
– Native apps or Mobile browser delivery or Hybrid?
• Challenges with Implementing SCORM on Mobile
– Dated API instance & wrapper algorithm
– User experience
– What is required?
– Using Mobile Frameworks & AJAX (to develop content)
– LETSI RTWS
– ADL Research
4
Friday, June 24, 2011
6. Last Year’s Use Cases
• Mine Lab (Taiwan): SCORM Reader on mobile, PAD SCORM
• Bank of America (GoLearn) & Accenture
• Upside Learning
• Litmos (recently acquired by Callidus Software Inc)
• OnPoint Digital (Cell Cast)
• CERTPOINT
• Rustici Software
6
Friday, June 24, 2011
7. New Use Cases?
• Mobile Learning Environment (MoLE) - 2011
(http://www.mole-project.net)
– share learning between U.S. and multi-national partners
– focus on the reconstruction of healthcare and areas of conflict or
natural disaster
• Sponsored by:
– Office of Naval Research Global (ONRG)
– The Coalition Warfare Program (OUSD(AT&L)/International Cooperation)
– The U.S. Air Force European Office of Aerospace Research and
Development (EOARD)
– The Telemedicine and Technology Research Center (TATRC)
7
Friday, June 24, 2011
8. MoLE - SCORM Use Case
• Integrating with ATLAS Pro for Joint Knowledge Online (JKO)
• Not trying to improve the LMS interface via mobile
• Looking at browser-based VLE to administer content
• Using HTML5 + Native App (Hybrid Solution)
• Working on both online/offline solution
• Using custom web services solution to receive basic SCORM data
• 2 Layers - One to LMS, second to App back-end
• Primary Goal of Project: Most effective user experience
• Tracking both informal and formal content
• Including Mobile TIP course (ADL) as part of prototype
8
Friday, June 24, 2011
9. New Use Cases?
• US Joint Knowledge
Development and
Distribution Capability
(JKDDC) - 2010
– Prototype targeted for
iPod Touch, iPhone, iPad,
and Android devices
– SCORM 2004 3rd Edition
– Tracking cmi.learner_id,
cmi.learner_name,
cmi.exit,
cmi.completion_status
online/offline
9
Friday, June 24, 2011
15. Implementation Challenges
• Frames are deprecated in HTML5
• Pop up windows are not consistently supported on mobile
• Most SCORM LMS / API Instance Implementations use frames or
pop up windows
• Using the Mobile Web Browser can result in a poor user experience
• Offline tracking is a challenge
15
Friday, June 24, 2011
17. Potential Work-Arounds
• LMS API instance that supports AJax or Web Services or Both?
• Develop content using AJax or a framework that inherently
supports it
• LETSI RTWS (SOAP for SCORM)
17
Friday, June 24, 2011
19. jQuery Mobile Framework
• Web App Framework based on Progressive Enhancement Approach
and Responsive Design techniques (Using CSS @ Media Queries)
• Easy to setup, optimized for mobile browsers, requires knowledge
of HTML (advanced techniques require knowledge of CSS &
JavaScript)
• Page is rendered with a normal HTTP request, and subsequent
"pages" are then requested and injected into that page's DOM
19
Friday, June 24, 2011
20. LETSI RTWS
• LETSI Run-time Web Services for Learning Project (RTWS)
• Creates a web services implementation of the SCORM run-time
communications protocols (alternative to JavaScript)
• Limited to the a small and specific set of functionality
• Scope of RTWS communication is limited to "single SCO"
courseware
• Benefits:
– Out of browser experiences
– Offline and occasionally connected training
– Removing cross domain scripting limitations
– Enabling delivery on alternative devices and formats
– Security
• http://letsi.org
• http://pipwerks.com/2010/11/17/soap-for-scorm/
20
Friday, June 24, 2011
24. Final Thoughts on Mobile
• Is it a requirement for mobile?
• Plan for the Disconnected Mobile User
• Don’t build browser content that uses pop up windows or frames
• Many native app commercial solutions available
• Web service implementations
24
Friday, June 24, 2011
25. More mSCORM Resources
• Mobile Learning Shareable Content Object Reference Model (m-SCORM
Limitations and Challenges [N09-35] – Office of Naval Research (ONR)
Science & Technology (Global) by Tribal (2010)
– URL: http://www.mole-project.net
• Guide for Best Practices on Mobile Web: An Adaptation for Web
Development with SCORM 2004
– URL: http://www.adl-ilce.org.mX
• Guide for Mobile Web Development with SCORM 2004: An Easy Way to
Start Developing SCORM Objects for Mobile Devices
– URL:http://www.adl-ilce.org.mx
• Instructional Design for Mobile SCORM: A Quick Guide for Developing
Content for Mobile Devices in SCORM 2004
– URL:http://www.adl-ilce.org.mx
• SCORM Implementation Strategies for Mobile (2010) by Jason Haag (ADL)
– URL: http://www.slideshare.net/jhaag75/
25
Friday, June 24, 2011
26. ADL mLearning Guide
http://mlearn.adlnet.mobi or http://mlearn.adlnet.gov
Friday, June 24, 2011
27. ADL mLearning Guide
http://mlearn.adlnet.mobi or http://mlearn.adlnet.gov
Friday, June 24, 2011
28. ADL mLearning Guide
http://mlearn.adlnet.mobi or http://mlearn.adlnet.gov
Friday, June 24, 2011
29. ADL Mobile Wiki
http://adlmobile.wikispaces.com
27
Friday, June 24, 2011