Splunk AppDynamics supports monitoring for hybrid applications based on the iOS/Android native SDK.

Hybrid Applications

Hybrid applications are web applications running inside an Android or iOS native shell. The web application can be in the form of an Android WebView or an iOS WKWebViews.

Hybrid Use Cases

Mobile RUM supports native mobile applications that run web applications or web views. Examples of this are Android WebViews and iOS WKWebView.

Hybrid Application Instrumentation Requirements

For instrumenting hybrid apps, you are required to:

  • Manually instrument the iFrames with the JavaScript Agent. For mobile native applications, the JavaScript Agent is injected into the top-level WebView or WKWebView instance, not in embedded web pages (iFrames). 
  • Use Android WebViews or iOS WKWebView for hybrid applications with embedded web views. 

Instrumentation Steps

To monitor your hybrid applications, you will need to set up and access Mobile RUM and follow the steps below based on your hybrid use case:

Native iOS ApplicationNative Android Application
  1. Instrument an iOS Application 
  2. Configure Hybrid Support for the iOS Application
  1. Customize the Android Build
  2. Instrument an Android Application
  3. Configure Hybrid Support for Android Applications

How it Works

For native Android/iOS applications, the Android Agent or iOS Agent will inject the JavaScript Agent into an Android WebView or iOS WKWebView. 

The diagrams below provide an overview of how Mobile RUM is used to monitor mobile native applications.

Mobile Native Application Architecture
Mobile RUM Architecture Diagram


1 Icon You instrument your mobile application with either the Android/iOS Agent.

2 Icon When your mobile application instantiates a WebView or WKWebView instance, the Mobile Agent injects the JavaScript Agent into it.

3 Icon The JavaScript Agent monitors the performance and WebView usage.

4 Icon The JavaScript Agent reports the application activity by sending beacons to the Mobile Agent.

5 Icon The Mobile Agent repackages the browser beacons into mobile beacons and sends the beacons to the EUM Server.

Mobile Agent and JavaScript Agent Compatibility

When hybrid app support is enabled, the Mobile Agents use an embedded JavaScript Agent to monitor mobile web pages. If you are already monitoring the same mobile web pages with a browser application, the JavaScript Agent version used to instrument the browser application may be different than the JavaScript Agent version used by the Mobile Agent. If the two versions of the JavaScript Agent are incompatible, the Mobile Agent will not be able to instrument web views or access event notifications from web views.

How to Ensure Compatibility

To ensure compatibility, browser applications should use JavaScript Agent version >= 4.5.4 and mobile applications should use Mobile Agent versions >= 4.5.5. When using compatible versions of the JavaScript Agents, the JavaScript Agent of the browser app will report beacons for a web page, and the embedded JavaScript Agent of the mobile app will be ignored and not report beacons because a web page cannot be instrumented with the JavaScript Agent multiple times. 

If you have disabled the Mobile Agent's hybrid app support, there will be no compatibility issues regardless of the JavaScript Agent version used by the browser application.

Troubleshooting Incompatible JavaScript Agent Versions

If you are using incompatible versions of the JavaScript Agents, do one of the following to correct the problem:

  • Upgrade the JavaScript Agent that you are using to instrument the browser application.
  • In the mobile instrumentation, disable the hybrid support (iOS/Android), so that the mobile web pages are only instrumented by the browser application instrumented with the older version of the JavaScript Agent.

Hybrid Application Network Requests

Network calls made in the context of the WebView show up as Ajax calls from the JavaScript Agent.