Chapter 3 | Create Sandbox App Listing
Users will create a New Sandbox App Listing that can be uploaded to MOTAR Studio.
Last updated
Users will create a New Sandbox App Listing that can be uploaded to MOTAR Studio.
Last updated
Chapter 3 Tutorial Video
3.1. Users will LOG IN to MOTAR STUDIO to create a new Sandbox App Listing.
3.2. To create a new app, CLICK the APP ICON found in the listing selection.
3.2.1. UPLOAD the APP ICON provided below for download.
To download the file, CLICK the LINK below. When the image opens in a new tab, RIGHT CLICK and select SAVE IMAGE AS to save as an image (.png file type).
Image scanning may take several minutes. Users may either wait until complete or exit the File Upload modal and continue with Step 3.2.2. (the user must CLICK the I UNDERSTAND button to exit the modal). Image scanning will continue in the background and users can resume with step 3.2.1.1. once scanning is complete.
3.2.1.1. After the secure scanning is complete, CLICK CLOSE on the file upload modal.
3.2.2. SELECT the SANDBOX App Environment.
"Sandbox" apps can only interact with test data (for testing integration) and are set to Not MIAB Compatible.
3.2.3. INPUT the APP NAME and SHORT DESCRIPTION.
The App Name must be unique. Highly recommend including the creator’s initials in the title to ensure there is not a duplicate in the system.
For example, the user Tim P. Smith would input the Course Title: TPS Alien Invasion.
App Name cannot contain symbols (i.e. hyphen -, slash /, comma ,).
3.2.4. CLICK the SAVE button to complete the creation of the Sandbox App Listing.
3.2.5. The user is redirected to MOTAR Sandbox and the new Sandbox App Listing is the first app visible in the list.
3.3. The user can now adjust the new Sandbox App Listing’s settings. CLICK the EDIT PENCIL ICON in the ACTION column of the listing cell to open the Preview of Listing page.
3.3.1. CLICK on the SETTINGS tab.
3.3.1.1. CLICK the PERMISSION SCOPES tab in the Settings menu.
Authentication and Profile scopes are set by default. These scopes enable authentication in the application, using SDK / API calls.
3.3.1.1.1. CLICK the + ADD SCOPE button to add the Training Scope.
This is an important step, as scopes help enable API interaction within the application.
3.3.1.2. CLICK the KEYS tab in the Settings menu.
3.3.1.2.1 CLICK the GENERATE CLIENT ID button to generate a Client ID.
Generated keys are unique to each app listing and are used to identify the application when making API calls to MOTAR. The Client ID is a public identifier for the application.
3.3.1.2.2. CLICK the SHOW SCRET button to generate a Client Secret.
The Client Secret identifies the application on the backend when making an API Request. It’s known only to the authorization server and the application. Essentially, it serves as the application’s password.
3.3.1.3. CLICK the DISTRIBUTION tab in the Settings menu.
3.3.1.3.1. CLICK the + ADD DISTRIBUTION button to configure Supported Devices and Distribution options.
A distribution option is required to publish an application to the MOTAR Platform. Distribution options allow the user to develop their app once, then deploy it across multiple devices.
3.3.1.3.1.1. VERIFY the Demo Release TOGGLE BUTTON is set to NO.
Demo is only applicable to Production applications, not the Sandbox environment.
3.3.1.3.2. POPULATE the VERSION.
For the purpose of this tutorial, the version entered will not impact the tutorial outcome.
3.3.1.3.3. POPULATE the RELEASE NOTES.
For the purpose of this tutorial, the release notes entered will not impact the tutorial outcome. Recommend a note such as: Tutorial App for MOTAR Lab.
3.3.1.3.4. Under the Supported Devices section, CLICK the CHECKBOX(ES) next to Supported Devices for this application: Meta Quest 2 and/or HTC Vive Focus 3.
Please indicate the device you are building the tutorial app to run on. If unknown or the user doesn’t have a VR device, select Meta Quest 2 or HTC Vive Focus 3 (this won’t impact the tutorial/demo outcome).
Selecting MOBILE ANDROID or MOBILE iOS will enable the user to select APP STORE LINK in the Distribution Model section. This feature will not be utilized for the tutorial.
3.3.1.3.5. Under the Additional Gear section, at the user’s discretion, CLICK the CHECKBOX(ES) next to applicable Additional Gear (includes Simulators, Controllers, and Haptics). CHOOSE either OPTIONAL or REQUIRED for each selection.
For the purpose of this tutorial, the Additional Gear(s) selected will not impact the tutorial outcome.
3.3.1.3.6. SELECT the option EXTERNAL URL in the Distribution Model section to create a distribution package.
3.3.1.3.7. POPULATE an EXTERNAL URL. For example, https://www.dynepic.com.
For the purpose of this tutorial, the URL entered will not impact the tutorial outcome.
3.3.1.3.8. POPULATE the RECOMMENDED SYSTEM REQUIREMENTS.
For the purpose of this tutorial, the requirements entered will not impact the tutorial outcome.
3.3.1.3.9. POPULATE the SPECIAL INSTALLATION INSTRUCTIONS.
For the purpose of this tutorial, the instructions entered will not impact the tutorial outcome.
3.3.1.3.10. CLICK the SAVE button at the bottom of the modal to add the app distribution.
3.3.1.3.11. CLICK the TOGGLE button to the right of the GO TO URL button to activate the distribution.
This action will activate the UPDATE button.
3.4. CLICK the TOGGLE button to update the status to SUBMITTED & UNAPPROVED.
3.4.1. CLICK the UPDATE button to update the Sandbox App Listing’s settings.
3.4.2. All requested changes will now be displayed on the Preview of Listing page. The page can be accessed by selecting SANDBOX from the MOTAR Studio menu bar, then selecting APPS from the Sandbox dropdown menu.
