MOTAR Studio currently supports App, Video, and Model listing creation. To add a new app, click the App icon found in the listing selection UI.
Create App Listing
Clicking the App Tile will push the user to the Create App Listing Flow. Here you have the ability to set up the app listing for its presentation in MOTAR Hub. Each App Listing will include App Type* - Sandbox or Production along with user input fields for App Name*, Short Description* and optional Preview Images and Preview Videos.
Apps in "sandbox" can only interact with test data (for testing your integration). "Production" apps are live in the MOTAR network.
Preview App Listing
After completing the App Listing flow, as a user you are able to Preview Listing Page, giving you a preview of your HUB Listing before it's active on the platform.
Add Scopes to your application using the "Add Scope" button and modal. This is important, scopes help enable API interaction within your application.
Authentication + Profile scopes are set by default. These scopes enable authentication in your application, using SDK / API calls.
Generate Key pairs (Client ID & Client Secret) on this tab in-app settings. Generated keys are unique to your app listing. These values are used to identify your application when making API calls to MOTAR.
The Training Scope - enables API interaction with the MOTAR Training Dashboard.
On Launch Configuration, the user can configure a redirect uri & desktop launch uri. Read more information on the two values below:
What is a REDIRECT URI?: A redirect URI, or reply URL, is the location where the authorization server sends the user once the app has been successfully authorized and granted an authorization code or access token
The redirect URI is used on the authentication flow
What is a DESKTOP LAUNCH URI?: A desktop launch URI is a unique sequence of characters that identifies a logical or physical resource used by web technologies.
The desktop launch URI is used to launch lessons/desktop applications directly from the platform. Please note: The application has to be configured correctly before utilizing this feature.
Supported Devices and Distribution options are configured on the tab above on app settings. From this screen, as a user, you can add, edit, and delete distribution options.
Clicking Add Distribution presents the user with the modal seen below. Here you will input a version number, release notes, and select supported devices.
Mark the distribution as a "Demo Release" using the toggle found on the right of the modal below.
Add App Distribution supports an App Binary upload option or an "External URL". On this modal, the user can select multiple supported devices (as needed). Find export Instructions for supported devices below:
Publishing your application to the MOTAR Platform requires a distribuition option
Pair your Distribution Option with Additional Gear supported by the platform, shown below. Additional Gear support includes: Simulators, Controllers and Haptics
Upload File Type
.apk & Google Play Store (Production)
.ipa & Apple App Store (Production)
Below are step-by-step instructions for creating distribution packages, along with info on all platforms MOTAR supports.
Apple App Store
When selecting the Apple App Store Distribution model you will be required to enter the following information:
Version: This will be a user-defined version number.
App Store ID: This ID will be listed on your public app store listing URL, see screenshot for reference:
Google Play Store
When selecting the App Store Link Distribution model you will be required to enter the following information:
Play Store ID: This ID will be listed on your public play store listing URL, see screenshot for reference:
Play Store Intent: Setting the Play Store Intent value will launch the play store app and load the targeted page if it's not found on the device. See the example below:
market://. Launches the Play Store app to load the target page.
The following section contains more information on distribution package types.
.apk - App Binary
1. In Android Studio’s main menu, choose Build → Generate Signed APK.
The Generate Signed APK dialog box appears. This dialog box has a drop-down list in which you select one of your project’s modules.
2. Click Next
As a result, another Generate Signed APK dialog box appears. This box contains a Key Store Path field. In what follows, it’s assumed that you haven’t yet created a key store. (If you’ve created one, you’ll know that you did.)
3. Click the Create New button.
As a result, a New Key Store dialog box opens.
4. Key Store
Choose a name and a location for your key store. Put the full pathname (the location and filename) of the new key store in the dialog box’s Key Store Path field. Enter passwords in the Password and Confirm fields. remember the passwords that you create when you fill in the Password and Confirm fields. You’ll need to enter these passwords when you use this key to sign another app.
In a key store file, each key has an alias
5. Accept the default validity period (25 years).
If you create a key on New Year’s Day in 2016, the key will expire on New Year’s Day in 2041. Happy New Year, everybody! According to the Play Store’s rules, your key must not expire until sometime after October 22, 2033, so 25 years from 2016 is okay.
6. In the Certificate section, fill in at least one of the six fields.
Click OK. As a result, the Generate Signed APK dialog box reappears. This time, many of the box’s fields are filled in for you. Click Next. When you do, one last Generate Signed APK dialog box appears. In this final Generate Signed APK box, take note of the APK Destination Folder. Also, be sure to select Release in the Build Type drop-down list.
7. Click Finish
Your .apk will be stored on your device. If using android studio during this setup the IDE will offer to open the file location of the .apk you just created.
Oculus, HTC, Varjo, HP, HoloLens, Magic Leap, and Pico Headsets:
Instructions supporting VR distribution can be found through the unity export options. After following those instructions take the final exported product, zip it, and upload it as a distribution option.
Go to File.
Go to Build Settings.
Go to the player settings tab in that dialog box.
Configure your game settings (screen splash,game name,company name,etc,etc)
Select your platform (win/mac/linux/xbox/etc etc)
Click on build.
In: Project > Description
Set the project’s details and thumbnail:
> The Project thumbnail will appear in the UE4 Editor browser.
> Thumbnail image must be a 192 x 192 resolution PNG
In: Project > Maps & Modes
Set default level (Map) for the project:
In: Project > Packaging
Choose build configuration
> For final distribution choose ‘Shipping‘:
In: Project > Supported Platforms:
Make sure Windows is selected:
Exporting the package
Creating the game package:
File > Package Project > Windows > Windows (64-bit)
And select an output folder.
A folder named “WindowsNoEditor” will be created,
And inside it will be the game executable along with code and assets folders.
This package can be renamed and copied to other locations.
Push notifications can be configured for your mobile application. Follow the IOS or Android platform guides listed below:
Notifications Overview | Android Developers
Notifications - Apple Developer
The SDKs tab within the Create App Listing Flow contains direct links to the MOTAR Swift and Unity SDKs repositories.
Permissions are set using the Permissions Wizard tool, read more information on the documentation page linked below.