Five Steps to Getting Started with the Native Mobile SDKs

Overview

The initial integration of MXO with your native mobile app solution, using the Mobile SDKs, consists of five main steps.

Estimated time to complete these steps is between one and three days, depending on your requirements.

Step 1: Integrate and Initialise the SDKs in your App

Follow the steps outlined in the links below:

Step 2: Ensure Customer Keys are being captured and sent to MXO

You can capture customer keys:

Step 3: Deploy the Admin mode build and make available to Business Users

After creating your Admin mode build, deploy it to business users to complete the configuration.

You’ll have already read the instructions related to creating and deploying your Admin mode Build as part of Step 1.

For a recap, see:

We recommend adding the Admin mode function on your internal builds, behind a debug settings function or on a dedicated build pipeline. For example:

Mobile - CI Example 1

Alternatively, you could add the Admin mode function behind a specific username you can use to log in to your app. For example:

  • You can configure the SDK in User mode as your app starts
  • You can then turn Admin mode on, dynamically, by logging in to the app using that specific username.

Mobile - CI Example 2

Head over to our documentation about Creating Touchpoints and Interaction Points to find out more about using Admin mode to capture customer activity and data, automatically.

Step 4: Final QA

After the business stakeholder signs off the SDK configuration, you’ll be ready to release it to the app store with your next scheduled app release. Before release, check that you’ve covered your desired use cases and completed full QA testing on your User mode build.

Step 5: Release your App

After testing is complete, release your app with the associated User mode build of the SDK to your customers on the respective App and Play Stores.

Top