Catch Android ANRs while users are stuck, not after they quit.
Appxiom finds the crashes, ANRs, memory leaks and failing API calls in your Kotlin, Compose and Java app, and ranks them by the user flows they break. Every issue comes with a stack trace and a timestamped trail your coding agent can read.
Android 6.0+ (API 23)Two Gradle lines and one call in your Application classWorks with Android Studio, Claude Code, Codex and Cursor
- Kotlin
- Java
- Jetpack Compose
- XML Views
- Activities and Fragments
- OkHttp and Retrofit
- Gradle and version catalogs
Set up in a few minutes
Add the dependencies and call Ax.init in your Application class. That one call turns on crash, ANR, leak, memory, startup and frame monitoring.
- kotlin
// build.gradle.kts releaseImplementation("tech.appxiom:appxiomcore:2.1.0@aar") { isTransitive = true } debugImplementation("tech.appxiom:appxiomdebug:2.1.0@aar") { isTransitive = true } // Application class override fun onCreate() { super.onCreate() Ax.init(this, appKey, platformKey) }Using OkHttp or Retrofit? Wrap your client builder with
OkHttp3Clientto monitor API calls.
What Appxiom catches in your Android app
Stability
Crashes in debug and release builds, with stack trace and device state Caught exceptions you choose to report Process kills on Android 11+: ANR exits, low memory kills, resource limits and startup failures
Responsiveness
Memory
Network
The bug your crash-free rate doesn't count
An ANR doesn't crash your app, so it never touches your crash-free rate. It still counts against you: Google Play treats a user-perceived ANR rate above 0.47% as bad behavior.
Appxiom reports an ANR when the main thread has been blocked for 5 seconds, while the user is still looking at a frozen screen. If they force-close the app, that becomes its own report. On Android 11 and later, the OS's own record of the ANR follows on the next launch. Each report carries the stack trace and the steps the user took before it.
- On by default, in debug and release builds
- The stack trace from the moment of the freeze
- The taps and screens that led up to it
Android Vitals tells you your ANR rate went up. Appxiom tells you which screen, which tap, which users and which flow.
Find leaking screens in production
A leaked Activity rarely shows up on your emulator. It builds up over long sessions on real devices until the app runs out of memory. Appxiom reports leaks from your release builds and names the screen, so you know where to look. In debug builds it goes down to the exact object.
Keep LeakCanary in debug if you use it. Appxiom tells you which screen to point it at.
Fix the bug that costs you orders first
Two issues land in the same release.
The photo crash. The profile photo cropper crashes on one manufacturer's phones. It has the most events this release, because the same few users keep retrying.
The Place order ANR. Tapping Place order saves the cart on the main thread. On low-memory phones the screen freezes for over 5 seconds. Nothing crashes. Some users wait. Some close the app.
Sort by event count and the photo crash goes first. Sort by Goal Friction Impact and the ANR goes first, because it sits inside your place_order goal and completed orders dropped this release.
val goalId = Ax.beginGoal(this, "place_order") // checkout opens
Ax.completeGoal(this, goalId) // order confirmedTwo calls per goal. Your coding agent can find your key flows and add them with the goals skill, once you approve.
Goal Friction Impact is part of the Professional plan.
Every step before the bug, with timestamps
Appxiom records Activity and Fragment lifecycle, Compose navigation, taps and your own markers. Each entry has a timestamp and the device's free memory. Each bug report carries the last 60 events before the issue.
| Event | Time | Free memory |
|---|---|---|
| CheckoutFragment: onResume | 19:42:10.215 | 14% |
| Clicked "Place order" | 19:42:16.880 | 12% |
| ANR, main thread blocked | 19:42:21.904 | 9% |
There is no screen recording. The trail is plain text, so your coding agent reads it directly, at a fraction of the tokens a video replay would take.
From a frozen Place order tap to a fix in Android Studio
Connect Appxiom's MCP server to the agent you already use: Gemini in Android Studio (Agent Mode), Claude Code, Codex, Cursor, Antigravity or any client that supports remote MCP.
Check Appxiom for the top ANRs in the latest release and fix the one in place_order.
Your agent gets the ranked issues, the stack trace, the Activity Trail and the device state for each one. You review the change like any other. At release time, the deobfuscation skill has your agent back up mapping.txt, so R8 stack traces can always be retraced.
Goal rankings and Quality Score need the Professional plan.
Built for Kotlin, Compose and Java
Kotlin and Views. Activity and Fragment lifecycle and taps are captured with no extra code.
Jetpack Compose. Pass your NavController to Appxiom and every screen lands in the trail. Button taps are recorded automatically.
Java. Every API has a Java form. One SDK covers your older Java screens and your newest Compose ones.
Moving from another tool?
See how Appxiom compares with
Priced per app, not per seat
Starter is $10 a month per app for every 10,000 monthly active devices, and detects every issue type. Goal Friction Impact, Quality Score and issue distribution come with the Professional plan. Every plan has unlimited seats, and every app gets a 30-day free trial.
Frequently Asked Questions
See what your Android users actually hit
Add Appxiom, ship a build, and see your ANRs, leaks and broken flows ranked by what they cost you.
We use cookies to improve your experience.