Android
Investigate Android app behavior by reviewing screenshots, gestures, logs, and performance alongside live app inspection.
Connect a visible Android issue with the user actions, runtime events, and app state around it. Ansight gives developers and agents session evidence to review and guarded tools to inspect the running app.
The native Android SDK exposes Kotlin-friendly APIs for Ansight telemetry, durable crash capture, network evidence, purchase diagnostics, host pairing, live session transport, artifacts, and remote tools including Clipboard.
Open your app repository in a coding agent and send this prompt:
Copyable prompt:
Use https://www.ansight.ai/skills/android/ansight-install-android.md to install Ansight in this native Android app. Keep it in a development build, verify a connected session, and show me the changes.
The setup guide has the manual steps.
Quickstart
Add the all-in-one package to the app module’s development configuration:
dependencies {
implementation("ai.ansight:ansight-android:latest.release")
}
See Android Packages when you need a core-only or individually assembled tool setup.
Put this code in your app’s Application subclass, usually
app/src/main/java/<your-package>/MyApplication.kt, inside onCreate() after
super.onCreate(). Register the class with
android:name=".MyApplication" in AndroidManifest.xml. Keep MainActivity
for UI and pairing flows that need an activity.
import ai.ansight.Ansight
import android.app.Application
class MyApplication : Application() {
override fun onCreate() {
super.onCreate()
if (BuildConfig.DEBUG) {
Ansight.initializeAndActivate(
application = this,
options = Ansight.developerOptions(clientName = "Android App"),
)
}
}
}
Ansight.developerOptions(...) applies the Android all-in-one developer preset: 400 ms sampling, 120 s retention, FPS, touch capture, JPEG capture every 2000 ms at quality 60 and max width 480, host auto-probe, full tool access, and all standard native tools including Clipboard. Purchase tools require separate opt-in registration.
Important: Screen capture will result in an FPS drop while the SDK captures, encodes, and transports frames. Disable session JPEG capture for trend-focused runs unless visual evidence is required.
Next steps
- Android Setup: complete the guarded startup and verify the connection with the CLI.
- Android Security and Tools: review the safeguards before enabling remote inspection in an app build.
- Pairing: connect a physical device.
- Crash Capture: review how native crash evidence is retained.
- Network Capture: record sanitized, typed requests.
- Connectivity Capture: record OS connection state, transport changes, and supported quality estimates.
- See Native Offline Capture for disconnected recording and host transfer across mobile SDKs, implemented after SDK 1.8.0.
- Android Motion Capture: forward shakes and accelerometer samples observed by the app.
- Clipboard Tools: access the device clipboard.
- Purchase Diagnostics: validate Google Play integrations on an emulator.
- File Descriptor Diagnostics or JNI Reference Diagnostics: investigate resource leaks.