The process of getting online learning from planning to posting can be arduous, time- and resource-consuming, and require hundreds of hand-offs between team members. Every measure must be taken to expedite each step along the way in order to make online learning relevant and timely to learners and therefore provide organizational benefits equal to costs. Adding mobile deployment to this equation only further complicates it.

You’re all excited about the promise of an Experience API-enabled world, but you’ve still got a learning management system (LMS) and a whole host of SCORM-based courses. Now what? In most cases, you’ll need to manage the transition—read: republish your library for the Experience API (xAPI)—over the months and years to come. But what if you could get the most out of both an LMS and a learning record store (LRS) at the same time as you move to your next-generation learning-and-performance infrastructure?

Instructional designers tend to define what is possible by the limitations of our chosen authoring tools. We remove ideas like responsive courses from consideration because our authoring tool does not support the capability. Sometimes common modern web practices don’t always transfer over to eLearning authoring tools until it is too late. Why not take control over what you can do in your eLearning authoring by building it yourself?

From the first desktop PCs to today’s cutting-edge smartphones, technology has a history of fundamentally changing the expectations of learning and development programs. We are now on the cusp of another technological advance, one that will once again change some of our definitions and how we address performance issues: wearable technology. This technology will come in various forms, but the one that many expect to serve as a quantum leap forward is Apple Watch. 

When organizations make the move to mobile, one of the first barriers they encounter is how to handle all of their existing content. Many organizations have large amounts of legacy content that needs to be accessible on mobile devices. Just republishing for mobile without redesigning the content does not make an effective mobile learning experience.

For many organizations, mobile learning has a limited outlook. They have taken the desktop eLearning paradigm and simply applied it to mobile technologies. But that view does not take into account the differences between mobile and desktop environments, nor does it take advantage of the uniqueness of the mobile platform.

It's all about flexibility. In this new age of eLearning, where our content is being accessed on all sorts of devices, our animations need to step up and be responsive. 

One of the most popular authoring tools in use today is Articulate Storyline. As more organizations make the move to mobile, the need to find ways to use Storyline for mobile projects increases. But where do you start? 

There is a frustration on the part of many HTML designers and instructional designers. While they would love to be able to place content directly on an iPhone or iPad as a native app, they soon realize that a solid knowledge of Xcode is required. If you want a native experience without having to learn iOS, Android, and BlackBerry (soon Windows 8) native development, then Titanium is the perfect solution.

Visuals are an important part of eLearning, and this importance and challenge only increases when you are working on the smaller screens of mobile devices. Understanding how to tweak your visuals to work better in a mobile environment can take your mLearning projects to greater heights. 

Learning does not happen by turning a page. Everyone has seen the Next button page-turning courses and realized that it does not work. However, building engaging content that is interactive and helps with training can be complex. Most designers do not have the technical skills to build an interactive native application or an interactive book.

You’ve made a great eLearning course designed to be delivered over your intranet or the Internet. Part of it uses Flash, and your learners use a lot of devices that won’t display Flash. You need to rebuild the Flash parts using HTML5-compliant animations. How do you build a responsive site that all devices, from desktop and laptop computers to tablets and smartphones, can use?