Skip to main content
Appxiom Developer Docs

Detect broken user flows and the bugs that broke them.

Lightweight SDKs for Android, iOS, Flutter and Web that detect crashes, ANRs, app hangs, memory leaks, slow network calls and failing functions, then rank every issue by its impact on your users' goals. Agent Skills let your coding agent integrate the SDK for you, and the MCP server lets it debug production issues with real telemetry.

  • Agent Skills
  • MCP server
  • < 5 min integration
  • Offline queuing
AndroidiOSFlutterWeb
Open the dashboard →
1Install the Appxiom skillsterminal
npx @appxiom/android-skills add all
2Ask your coding agentClaude Code · Cursor · Copilot
  • Integrate the Appxiom SDK into this Android app using the Appxiom skills. Here are my App Key and Platform Key.
  • Track screens in our Jetpack Compose navigation and monitor OkHttp network calls.
  • Add Appxiom goals to the signup and checkout flows, then raise a test issue to verify.
Android skills guide →Manual setup guide →
Platforms

Choose your platform

Each guide covers requirements, installation, initialization and release setup for that platform.

Android

Kotlin · Java · Jetpack Compose
Start here: requirements →

iOS & iPadOS

Swift · Objective-C · SwiftUI
Start here: requirements →

Flutter

Dart · Android · iOS
Start here: requirements →

Web

JavaScript · TypeScript · React
Start here: requirements →
Quickstart

Up and running in four steps

  1. 1

    Create an app

    Sign in to the dashboard, add your app and copy its App Key and Platform Key.

  2. 2

    Add the SDK

    Add the SDK with Gradle, CocoaPods, pub or npm. Mobile apps get separate release and debug artifacts.

  3. 3

    Initialize

    Call Ax.init() (Android, Flutter), Ax.initialize() (iOS) or init() (Web) once at app start.

  4. 4

    Verify

    Raise a test issue with Ax.test() and watch it land in the dashboard.

AI coding agents

Integrate with your agent. Debug with it too.

Agent Skills let your coding agent add the SDK for you. The MCP server lets it read real production data, so the same agent that wrote the integration can find out why checkout broke.

  1. 1

    Install skills

    One npx command drops SKILL.md files into your agent’s skills folder.

  2. 2

    Agent adds the SDK

    Your agent wires up dependencies, init, network, goals and trails the right way.

  3. 3

    Connect MCP

    Point your agent at the Appxiom MCP server and sign in once.

  4. 4

    Agent debugs production

    Ask about real crashes, ANRs and drop-offs and get root-cause analysis in your editor.

Integrate

Agent Skills

Skill files that teach Claude Code, Cursor, Copilot or Antigravity how to add the Appxiom SDK to your project correctly, from dependencies to goals and trails.

  • coreGradle dependency, ProGuard rules, Ax.init() and exception reporting
  • composeCompose, Activity and Fragment screen tracking and leak detection
  • networkOkHttp3 and Retrofit telemetry with header masking
  • goalsFinds critical workflows and adds Ax.beginGoal / completeGoal
  • trailsActivity markers and breadcrumbs before every issue
  • test-issueTemporary test call to verify setup, removed before release
  • deobfuscationBacks up mapping.txt and retraces obfuscated stack traces
npx @appxiom/android-skills add all
# or pick one: npx @appxiom/android-skills add core

The CLI detects .claude/, .cursor/ or .agents/ in your project and installs there. Override with --agent claude|cursor|copilot|antigravity or --target <dir>.

Android skills guide →
Debug

MCP server

Connect your agent to live Appxiom data so it can investigate production issues without leaving the editor.

  • Crashes, ANRs, hangs and errors by app and release
  • Occurrence telemetry: stack traces, breadcrumbs, network and device state
  • Goal Friction Impact for your critical user flows
  • Quality Score and release stability trends
claude mcp add --transport http appxiom https://app.appxiom.com/ax/app/api/mcp

Opens a browser sign-in. If it doesn’t, run /mcp in Claude Code.

Then ask your agent
  • Check Appxiom for the top ANRs reported in the latest release.
  • Inspect the occurrence breadcrumbs and memory state for crash ID 2931.
  • Evaluate the Quality Score impact and goal friction for our checkout flow.
Setup guides
AndroidiOSFlutterWeb

MCP Skills

Teach your agent how to read Appxiom data, not just fetch it.

  • telemetryRoot-cause analysis across activity trails, function and network parameters, device and runtime state
  • severityClassify issues as fatal, major or minor from business impact and error rates
  • goalsRank goal conversion drop-offs, device impact and funnel health
  • qualityInterpret Quality Score, release stability and score trends
npx @appxiom/mcp-skills add all
MCP skills guide →
Detection

Detected automatically

No extra code after initialization. Every issue arrives with device context and the activity trail that led to it.

Crashes

Uncaught exceptions with stack traces, device state and the activity trail leading up to them.

ANRs & App Hangs

Main-thread blocks that freeze the UI, including app exits caused by ANRs.

Frozen & slow frames

Frame-rate drops and janky screens that users feel before they report them.

Memory leaks

Leaked objects, high usage and sudden spikes, reported with the screen they happened on.

Low memory warnings

System memory pressure events, including Android trim-memory signals.

Network failures

Failed, delayed and duplicate calls plus unexpected status codes on OkHttp, URLSession and more.

Slow screen loads

Screens that take too long to become usable, measured per screen.

App startup

Cold, warm and hot start times, so regressions show up per release.

High CPU usage

Sustained CPU spikes that drain battery and slow the device down.

App exits

Why Android killed your process: ANR, low memory, resource limits, signals, freezer or init failure.

Web errors

Uncaught errors, failed resource loads, frame drops and memory leaks in the browser.

Network capture settings

Whitelist hosts, mask sensitive fields and tune timeouts for captured calls.

Instrument what matters

A few lines of code catch the silent bugs that never crash.

Function tracking

Flag functions that return null, out-of-range or wrong values, run late or throw.

Feature failures

Catch async callbacks that are never called, the silent bugs that never crash.

Reported exceptions

Send caught exceptions and NSErrors you handle but still want to see.

Custom issues

Raise your own issue types for business rules that only your app knows about.

Prioritize

Fix by impact, not by count

Appxiom ties issues to the user journeys they break, so the bug blocking checkout outranks the noisy one nobody notices.

GFI

Goals & Goal Friction Impact

Wrap critical flows like signup or checkout with Ax.beginGoal() and Ax.completeGoal() (startGoal() / endGoal() on Web). Each bug gets a 0–10 score for how much it blocks that goal, so you fix what costs users first.

QS

Quality Score

One weighted score per app version built from crashes, ANRs, hangs, latency, leaks and drop-off. Compare releases at a glance.

Trail

Activity trail & issue distribution analytics

See the taps, screens and network calls before every issue, and track how each version trends over time.

FAQ

Common integration questions

The mobile SDKs are under 150 KB and the Web SDK loads asynchronously. Issues are batched and sent in the background, so the main thread is not blocked, and unsynced issues are the only thing kept on the device.
Dashboard →Create apps and get your keysSupport →Raise a request on our service deskBlog →Debugging guides and deep divesAll versions →Docs for older SDK releases