Definition

Launch 3rd party applications built with the Motive Lightweight SDK “LSDK”Connect Modules to Applications so that they can be launched with Launch Pad.

About

The primary use for this is with the LSDK. When creating a Module on Launch Server, you need to add Content. Content, up until now, has either been Storyflow Connections or Bundles (which are generated on Storyflow). Now, Content can also be an Application. Launch Pad allows Learners to launch their Modules from one place. In order for Launch Pad to launch the module, it needs to know which application the module runs in.

Example: A company has an existing VR training app. It has no relation to the Motive platform. The company wants to be able to launch their training from Launch Server. They can make a new build of their training app with the LSDK. The new build will not have the ability to connect with Storyflow but it can talk to Launch Server and report back data/results.Since a Module requires Content and, up until this point, Content required a bundle from Storyflow, a new Content type was needed. This new type is Applications3 different applications for training depending on the type of scenario they are running. They want to use Launch Pad to make it easier for their users to access the content. By configuring each module to point at a specific Application, Learners can launch Modules directly through Launch Pad and not worry about which app to run on the device.

Note that Applications can work with any application installed on the device, including legacy applications. They do not need to use Storyflow.

Applications can also take advantage of Launch features directly (LMS integration, data tracking, user management, etc.) by integrating LSDK.

...

We have video and text documentation of Setting up an LSDK with Launch Server and Launch Pad. If you are an Assembler, you can see the documentation in the links below.

...