The Connect SDK for Android captures how users interact with your app — screen views, gestures, taps, and exceptions — and delivers the data to Acoustic Connect for analytics, session replay, and audience targeting. It also enables identity-aware reporting and mobile push notifications.

What's included in your plan

Capability	Pro	Premium	Ultimate
Behavioral analytics	✓	✓	✓
Push notifications	✓	✓	✓
Identity signals	✓	✓	✓
Session replay			✓
PII masking in session replay			✓

What the SDK captures

Automatically

The SDK captures the following data without any additional code changes.

User interactions

Screen views — every activity and fragment transition, with logical page names for session replay navigation
Gestures — taps, double taps, tap and hold, swipes (horizontal and vertical), and pinch gestures; unresponsive gestures are highlighted in session replay
Form interactions — field focus, text changes, and form submissions
Navigation drawer open and close events
Dialog appearances and dismissals

Device and session context

At the start of each session, the SDK automatically records device characteristics (model, manufacturer, OS version, screen dimensions, pixel density), app metadata (name, version), locale, language, and orientation. During the session it tracks changes in network connectivity, battery level, and orientation.

Exceptions

Uncaught exceptions (crashes) — stack trace and device state at the time of the crash, captured automatically
Caught exceptions — captured when you call Connect.logException()

With additional setup

Capability	Description	Guide
Push notifications	Send targeted messages to your app users via Firebase Cloud Messaging (FCM) or Huawei Mobile Services (HMS). The SDK auto-detects the available provider on the device.	Firebase or Huawei
Identity signals	Match anonymous app visitors to known contacts in your Connect audience. Send an identity signal after sign-in or registration to enable targeted push campaigns and cross-channel attribution.	Sign-in and Registration
Custom events	Log any in-app event that isn't captured automatically — for example, a specific button tap or a business-significant action.	Event and data logging
WebView capture	Capture user interactions inside embedded Google WebViews for a complete session replay that covers both native and web content.	Improve session replay

Performance impact

The SDK is designed to minimize its footprint on users' devices:

Memory — approximately 2–3% additional memory consumption (based on benchmark testing; actual impact varies by device and app).
Battery — minimal effect on battery life.
Offline resilience — if the Connect collector is unreachable, the SDK stores captured data in memory (up to 400 KB per file, with up to 5 files cached). The oldest data is discarded if the cache grows beyond this limit. Data is sent automatically when connectivity is restored.

Requirements


Languages	Kotlin and Java
UI architectures	View-based (XML) and Jetpack Compose
Android versions	Android 8.0 (API level 26) to Android 16 (API level 36)
CPU architectures	All standard Android ABIs — the SDK is pure Kotlin/Java with no native binaries
Development environment	Android Studio Otter \| 2025.2.1 Patch 1 or later

Integration path

The Android integration is split into focused steps. Start with SDK integration, then add the features your app needs — identity and push are independent and can be adopted in either order.

Integrate the SDK into your app: View-based or Jetpack Compose
Identify users at sign-in and at registration
Enable push notifications: Firebase or Huawei
Move your integration to production

Sample apps

Two reference implementations are available:

Acoustic Connect Mobile Push Sample App for Android (XML) — View-based app
Acoustic Connect Mobile Push Sample App for Android (Compose) — Jetpack Compose app