Messaging and conversational experiences have transformed how businesses engage with their customers. When you add Mobile App Messaging directly within your app, you get:

  • Increased customer satisfaction with an ideal customer experience through an always connected, ongoing conversation.
  • Increased customer retention and engagement (stickiness of your app).
  • Consumers never miss a new message with push notifications.
  • Fully customizable customer experience including look and feel.
  • Optimized for network bandwidth and battery usage.

Sample screenshot Sample screenshot Sample screenshot

SDK support of XCFramework — a new format of packaging frameworks

From iOS SDK version 6.0 and up, the SDK will support the new XCFramework. The new format packages all dependencies under all target platforms and architectes into one single unified bundle, removing the version-lock in swift as well as eliminating the need to build a fat framework. This means that the installation process from V6.0 and up, and V5.2.1 and down, will have different steps to follow. We have two quick start guides that are dedicated to the different processes, which will help you to install the relevant version on your app.

Quick start guide for 5.2.1 and below

Quick start guide for 6.0 and up

Implementation considerations

To successfully deploy messaging within your mobile app, it’s important to understand that the SDK has several functions and tasks. We recommend you go through the following list before beginning your deployment.

  1. Supported and certified devices. Review the Conversational Cloud system requirements to find the list of devices supported and certified by the In-App SDK. For Android, you may need to deploy two different Android APKs (one with messaging and one without) if many of your users have unsupported devices.

  2. Authentication. The most important and possibly the most complex portion of your deployment. Determine if you are placing messaging in authenticated areas of your app. If so, consider the following:

  • Your mobile app user s should be able to log into your back-end securely.
  • Your back-end must be able to supply, upon request during the session, an OAuth 2.0 code (for Code Flow) or a JSON Web Token (JWT) (for Implicit Flow).

  1. Push Notifications. The key factor that makes the experience better for customers because they receive a proactive notification as soon as a reply or notice is available. Determine how you want the push notifications to work. You can use your own push service or use LivePerson’s.

  2. Control over the conversation window. Take full control of the window or customize the window provided by LivePerson.

  • Customize the window: Window mode
  • Full control of window: ViewController mode

  1. Customization and branding. Review the list of default configurations available for iOS to determine the features to enable.

  2. Callback behavior. Utilize LivePerson’s Callbacks and APIs to control or change the behaviors and actions of the messaging app. The SDK provides a callback mechanism to keep the host app updated on events related to the conversation. The SDK provides APIs to establish the server connection for messaging.

  3. Messaging in multiple languages. Utilize LivePerson’s default translations or override them with your own text and language adjustments. Language settings are based on the user’s phone language settings and app language settings. Override all settings and maintain your default language at all times.

  4. Data Masking. Determine if you require data masking for potentially sensitive data. If so, choose one of the two masking capabilities and then contact your Account Team or Support to have data masking configured.

  • Client-side masking: The data is masked in the conversation transcript, appearing as asterisks, but the Agent can read it.
  • Real-time masking: Both client and agent data get masked.
  1. Accessibility. Not all features available in the SDK support accessibility. You may need to turn off various features to be fully compliant.
  • Enter timeout and expiration controls:
    • endingMessageTimeoutInMinutes (60)
    • csatSurveyExpirationInMinutes (1440)
  • Disable shortcut to new messages feature:
    • scrollToBottomButtonEnabled (false)
    • scrollToBottomButtonMessagePreviewEnabled (false)
    • unreadMessagesDividerEnabled (false)
  • Disable link preview: enableLinkPreview (false)