Four Steps to Getting Started with the Hybrid Mobile SDKs

The initial integration of MXO with your hybrid mobile app solution consists of four main steps.

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

Unsupported Features

Due to the nature of hybrid app solutions, not all Mobile SDK features are supported.

Automatic Interaction Tracking

Typically, hybrid app solutions use non-native UI elements that the Hybrid SDKs are unable to recognize. For this reason automatic interaction tracking is disabled, by default, for both the Cordova and React Native SDKs. Automatic interaction tracking is enabled for the Flutter SDK, because you can add Flutter into a native app. We recommend disabling automatic interaction tracking, however, unless only part of your app uses Flutter.

Tip: If you do want to use automatic interaction tracking with the Flutter SDK information about the recommended configuration is available in the Flutter documentation.

With automatic interaction tracking being unavailable, you need to use the sendInteraction method to send information about customer interactions to MXO, when required.

For more information about using the sendInteraction method with each Hybrid SDK, refer to the documentation for that SDK, as follows:

Admin Mode

Admin mode provides you with an interface to add Interaction Points, Activity Capture Points, and Attribute Capture Points to native UI elements within a mobile app.

Typically, hybrid app solutions use non-native UI elements that the Hybrid SDKs are unable to recognize. For this reason, our hybrid SDKs do not support the Admin Mode feature.

If, however, you have integrated into a native app or your hybrid app contains native UI elements, for example, if you add Flutter to an existing app, you can enable and use Admin mode for those areas.

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 programatically, after a user successfully logs in to your app.

Step 3: 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 4: 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.