Skip to main content
Web apps in JavaScript, TypeScript and React

Your error tracker counts exceptions. Your users leave checkout over a slow API call.

Appxiom finds the JavaScript errors, failing API calls, memory leaks and frame drops in your web app, and ranks them by the user flows they break.

View demo dashboard

React 18 and 19Next.js, Vue, Angular and SvelteInstall from npmWorks with Claude Code, Codex and Cursor

  • JavaScript
  • TypeScript
  • React
  • Next.js
  • Vue
  • Angular
  • Svelte
  • Vite

Two lines of code in your browser entry point

Install the package and call init once, before your app renders. React apps use the React package, which adds component lifecycle events to the trail.

  1. javascript
    import init from '@appxiom/web'; // React: '@appxiom/4react'
    const ax = await init(appKey, platformKey, appVersion, buildId);

    The SDK runs in the browser. In Next.js, Nuxt or SvelteKit, initialize it on the client only.

The bugs that cost you sales often never throw

A slow endpoint, a button that sends the same request three times, a page that keeps leaking memory until the tab crawls. None of these show up as an exception, so a tool that counts errors misses them.

Appxiom reports each one as an issue, with the user's steps before it.

Fix the bug that costs you orders first

Two issues land in the same release.

The report error. A chart on an internal admin page throws a TypeError. A few admins open it all day, so it has the most events this release.

The slow coupon. On checkout, Apply coupon takes up to nine seconds on mobile networks. Nothing throws. Users tap again, the app sends duplicate requests, and some leave before paying.

Sort by event count and the chart error goes first. Sort by Goal Friction Impact and the coupon goes first, because it sits inside your checkout goal and completed orders dropped this release.

javascript
ax.startGoal('checkout-flow');
ax.endGoal('checkout-flow'); // order confirmed

Two calls per goal.

Goal Friction Impact is part of the Professional plan.

Every step before the bug, with timestamps

Appxiom records clicks on buttons and links, your own markers and, in React apps, component lifecycle events. Each bug report carries the last 60 events before the issue, each with a timestamp.

Example
EventTime
Checkout started14:06:51.208
Clicked "Apply"14:07:03.441
Clicked "Apply"14:07:04.512
Clicked "Apply"14:07:05.097
Slow response: POST /api/cart/coupon14:07:12.630

There is no screen recording. The trail is plain text, so your coding agent reads it directly.

From a slow Apply button to a fix in your editor

Connect Appxiom's MCP server to the agent you already use: Claude Code, Codex, Cursor, Antigravity, VS Code or any client that supports remote MCP.

Example prompt

Check Appxiom for the top friction in checkout-flow and fix it.

Your agent gets the ranked issues, the stack trace, the Activity Trail and the browser details, then disables the button while the request is in flight. You review the change like any other.

Goal rankings and Quality Score need the Professional plan.

Moving from another tool?

See how Appxiom compares with Crashlytics, Sentry, Datadog and BugSnag.

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. On the web, a device is one browser. 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.

See pricing

Frequently Asked Questions

See what your web users actually hit

Add Appxiom, ship a build, and see your errors, slow calls and broken flows ranked by what they cost you.

Read the web docsView demo dashboard

We use cookies to improve your experience.