On mobile?
Email yourself the setup link so you can finish when you're at your computer.
✓ Email sent! Check your inbox.
× Failed to send. Please try again.
⏱ Too many attempts. Please wait a few minutes and try again.
AppAmbit records the trail automatically: every screen, every lifecycle event, every session, in order. So the moment something breaks, the steps that led there are already attached. See the full trail in your dashboard, or ask your AI Agent to read it over MCP.
Works on iOS and Android. Pairs with crash monitoring and the session timeline.
Every step, dropped on its own, in order.
No code to place a single marker.
Views, lifecycle and sessions, captured.
The exact sequence the user took.
The trail is attached when it breaks.
Call start() once and the trail builds itself. From then on, every lifecycle change, screen view, and session boundary is captured for you, on iOS and Android.
App start, resume, pause, and background, captured as they happen.
Every screen and page the user opens, recorded in navigation order.
Session start and end, with duration, so each trail is scoped to one visit.
Read the trail yourself in your AppAmbit dashboard, or point your AI Agent at it over MCP. It walks the same markers and hands you the exact steps the user took, right up to the crash.
See the whole picture in the session timeline, next to the crash report.
you › What did users do right before the spatial-audio crash?
→ appambit.breadcrumbs.query(session: "sess_9f21")
They enabled spatial audio, then the audio manager crashed.
Breadcrumbs are the markers, and the trail is what they add up to. You do not place them by hand: start the SDK and each one lands on its own, so a full trail is already there when you need it.
One call at launch. No per-screen wiring, no manual logging to keep in sync.
Each screen, lifecycle change and session boundary becomes a breadcrumb, in order.
Tracked events land in the same trail, right next to the automatic markers.
The trail rides along with the session and attaches to any crash on its own.
Every marker, colour-coded
You do not start from a bare stack trace. Read the session top to bottom: the app resumed, the user turned on a new feature, and the next line is the crash. The cause is right there in the steps, no reproduction needed.
See the whole picture in the session timeline, next to the crash and error report.
Breadcrumbs are the automatic markers your app drops as it runs. The session timeline is where those markers line up next to your logs, network calls and the crash, so you can read one whole session to its root cause.
The automatic trail of markers, on their own.
The full recording you read to the cause of a crash.
Start the SDK once. Lifecycle, screens, and sessions are recorded with no extra code.
Session timeline →The trail rides along with each crash report, so you see the steps that led there.
Crash & error monitoring →Tracked events land in the same session timeline, right next to the automatic breadcrumbs.
Events →Automatic signals and your own events sit side by side, in the exact order they occurred.
Every trail is grouped by session, bounded by its start and end, tied to the user and device.
Audience →Read the trail in your dashboard, or let your AI Agent query it over MCP.
MCP Agent →Start the SDK once and every session carries its own breadcrumb trail. See it in your dashboard, or ask your AI Agent to read it over MCP.
Every crash, with the trail attached.