Configuring the mobile co-apping collaboration layer
Mobile co-apping lets visitors share the view of a mobile app that has Unblu integrated into it with other conversation participants.
Prerequisites
Before you start configuring mobile co-apping in specific conversation templates, you must activate it. If you don’t, the configuration properties for mobile co-apping aren’t available in your conversation templates.
You can activate mobile co-apping in the GLOBAL or ACCOUNT scope with the following configuration properties:
-
com.unblu.license.account.featureMobileSdkVisitor must be defined.
-
Set com.unblu.messenger.mobileVisitorSdkEnabled to
true. -
Set com.unblu.messenger.mobileCoBrowsingEnabled to
true.
General configuration options
For information on general configuration options, refer to the section General configuration options of the article Configuring and manipulating collaboration layers.
Mobile co-apping configuration properties
| For mobile co-apping to work with your app, you first have to integrate Unblu into the app using the Unblu mobile SDK for Android or iOS. Read the appropriate sections of the Unblu documentation on iOS and Android integration for information on how to do so, and consult the mobile SDK references for Android and iOS. |
The following configuration properties determine where participants can launch a mobile co-apping session:
-
com.unblu.visitor.ui.engagement.showRequestMobileCobrowsingEngagementOption: Allow visitors to launch mobile co-apping from the Unblu welcome screen in a mobile app.
The following configuration properties allow you to customize mobile co-apping to suit your organization’s needs:
-
com.unblu.conversation.feature.mobileCoBrowsingEnabled: Enables mobile co-apping in the conversation template.
-
com.unblu.conversation.collaboration.approval.approveActivateMobile: Defines whether the context person must approve mobile co-apping.
If the mobile co-apping session would show the app of a participant other than the context person, that participant must also approve the mobile co-apping session.
-
com.unblu.messenger.startWithMobileCobrowsingOptionEnabled: Makes mobile co-apping available as an option to start a session.
-
com.unblu.conversation.collaboration.autostartLayers: Automatically launches a mobile co-apping session. If necessary, this first triggers an approval request.
-
com.unblu.conversation.collaboration.action.allowMarkInMobileCobrowsing: Enables mark mode in mobile co-apping sessions.
-
com.unblu.conversation.collaboration.approval.approveMarkMobile: Defines which types of participant the visitor must approve the use of mark mode for.
-
com.unblu.conversation.collaboration.action.allowStopMobileCobrowsing: List of participant types who may end a mobile co-apping session.
-
The indicator that there’s an ongoing mobile co-apping is configurable using the configuration properties in the group com.unblu.mobiledevice.v2.client.core.MobileCoBrowsingIndicatorConfiguration. The text properties used in the mobile co-apping indicator are in a group with the same name.
| There’s no remote control mode in mobile co-apping. |
Whether mobile co-apping captures only your app’s content or everything on the screen is set in the mobile SDK. Out-of-app capture continues while the visitor uses other apps. Private views and areas only hide content while your app is in the foreground. For details, refer to the Android and iOS articles on mobile collaboration layers.