|
This article covers the following: |
Overview
If your mobile application relies on WebView for rendering web content, you may be unsure whether to integrate Wingify Web Behavior Analytics or Wingify Mobile App Behavior Analytics. This article outlines key considerations, limitations, and recommendations to help you choose the right product.
When to Use Wingify Web Behavior Analytics
It is recommended to use Web Behavior Analytics if your mobile application is mainly or entirely WebView-based, meaning the entire user interface and interactions are driven by content within a WebView.
You must consider the following points if you use Web Behavior Analytics for tracking behavior on your WebView-based app:
- Web Behavior Analytics is designed to capture user interactions with web content displayed inside a WebView.
- JavaScript must be enabled within the WebView for Web Behavior Analytics to work correctly.
- WebView is powered by Chrome on most devices, so modern web technologies are supported seamlessly.
- On older Android devices, outdated Chrome versions may lead to compatibility issues.
- If your web content is hosted on an internal network or behind a firewall, snapshots of assets (CSS, images, etc.) may not render during session playback.
For detailed integration steps, refer to Configuring the Wingify SmartCode for Your Website.
When to Use Wingify Mobile App Behavior Analytics
It is recommended to use Wingify Mobile App Behavior Analytics if your mobile app includes native screens as well as WebViews.
If you rely solely on Web Behavior Analytics to analyze user behavior in a native app, it will only track interactions within WebViews and overlook activity on native screens. With Mobile App Behavior Analytics, you get a complete view of the user journey (both native screens and WebViews), though there are some platform-specific limitations inside WebViews:
- View Hiding - Individual elements inside a WebView cannot be hidden. You can only hide the entire WebView using the native view-hiding capability.
- Heatmaps - Dynamic heatmaps are not supported for web content inside WebView. For example:
- Scroll positions and attributes within WebView are not tracked.
- Heatmap visualizations will remain static for WebView content.
Recommendation
- If your app is entirely WebView-driven, use Wingify Web Behavior Analytics.
- If your app is a mix of native + WebView screens, use Wingify Mobile App Behavior Analytics.
Need more help?
For further assistance or more information, contact Wingify Support.