.svg)
Often the slowest part of fixing a mobile bug is figuring out what happened.
A customer opens your app, adds three items to the cart, and taps Checkout. The app freezes, then crashes. They don't file a bug report. They close the app, and maybe they finish the purchase somewhere else.
Your crash tool captures a stack trace. Your team gets a ticket that says "checkout crash, iOS." Then the guessing starts. What screen was the user on before? Was it the network? Can anyone reproduce it?
Often the slowest part of fixing a mobile bug is figuring out what happened. Breadcrumbs answer that question, and Blue Triangle's iOS and Android SDKs now record them automatically and send them to Jira, Slack, and AI assistants.
What are mobile app breadcrumbs?
Mobile app breadcrumbs are the time-stamped record of what a user did in your app and what the app did in response. Every screen view, tap, network request, and change in device state is captured in order.
For the checkout crash above, the trail looks like this:
Navigated to Cart → Tapped "Checkout" → API call to payment gateway → Network timeout → App crash
A crash report shows you where the code failed. Breadcrumbs show you how the user got there.
How are breadcrumbs different from crash reports and logs?
|
|
Crash reports |
App logs |
Breadcrumbs |
|
What it captures |
Stack trace at the point of failure |
Messages developers chose to log |
The sequence of screens, actions, network calls, and device state |
|
Question it answers |
Where did the code fail? |
What did the code report? |
What did the user experience, step by step? |
|
Business context |
None |
Rarely |
Cart value, order, campaign, and A/B test data (with Blue Triangle) |
What engineering teams get
- Bugs you can reproduce without guessing. The ticket shows the exact sequence of events, so nobody has to ask what the user did. That is where mean time to resolution (MTTR) comes down.
- A clear line between app and backend. Breadcrumbs tie each screen and tap to the network calls behind it. A screen frozen by a slow API looks different from a client-side bug.
- The device conditions at the time. Breadcrumbs record network switches (Wi-Fi to cellular) and memory use leading up to the problem.
- The step where users give up. See exactly where people abandon a flow, down to a specific checkout screen.
- A dollar figure on each bug. Tie errors to the journeys they interrupted and measure the revenue lost to each one.
- Real paths next to intended ones. Compare how people move through the app with how it was designed.
What product and business teams get
- The step where users give up. See exactly where people abandon a flow, down to a specific checkout screen.
- A dollar figure on each bug. Tie errors to the journeys they interrupted and measure the revenue lost to each one.
- Real paths next to intended ones. Compare how people move through the app with how it was designed.
How Blue Triangle captures breadcrumbs on iOS and Android
Our native SDKs record breadcrumbs without developers hand-logging each action. Four pieces build the trail.
1. Screen tracking
On iOS, the SDK tracks UIViewController screens automatically. SwiftUI screens need the bttTrackScreen() modifier. On Android, it tracks Activities and Fragments; Jetpack Compose screens use the BttTimerEffect side effect. You get a timeline of every screen a user visited.
2. Network capture
On iOS, NetworkCaptureSessionDelegate (or bt-prefixed URLSession methods) records request details. On Android, BlueTriangleOkHttpInterceptor and BlueTriangleOkHttpEventListener plug into OkHttp. Every API call lands on the timeline, so you can see which requests succeeded, failed, or stalled on each screen.
3. Native-to-WebView stitching
Many apps hand users off to a web view for checkout or account pages. Both SDKs stitch those sessions together (WKNavigationDelegate on iOS, WebViewClient on Android). A user who moves from a native product page to a web checkout shows up as one continuous journey.
4. Business context
Developers can attach checkout data (cart value, order number, cart count) and campaign data (A/B test IDs, traffic segments) to each session. That context lets you rank bugs by the revenue they put at risk.
Who uses breadcrumb data?
|
Team |
How they use breadcrumbs |
|
Developers and QA |
Reproduce bugs from the step-by-step trail and end the "works on my machine" back-and-forth. |
|
Product managers |
See how real users move through the app and where technical problems get in their way. |
|
Customer support |
Look up a specific user's session and see what happened, without asking a frustrated customer for technical details. |
|
E-commerce and marketing |
Match drop-offs to specific campaigns or A/B tests using the data attached to each session. |
Getting breadcrumbs to the people who need them
A breadcrumb trail only helps if someone sees it in time. Blue Triangle sends it to the tools your team already has open.
AI assistants, through our MCP server
The Model Context Protocol (MCP) is an open standard that lets AI assistants securely query outside data sources. Our MCP server connects assistants and agents to your Blue Triangle data. An engineer can ask, "What network breadcrumbs led to crashes on the iOS checkout screen in the last 24 hours?" and get a summary of the affected journeys without opening a dashboard.
Jira
When Blue Triangle detects a critical error or crash, it can open a Jira ticket with the breadcrumb trail, device state, screen history, and network logs already attached. The engineer who picks it up can start reproducing the bug right away.
Slack
Set alerts for specific problems, such as a spike in cart abandonment or a jump in Android network errors. Blue Triangle posts a summary and a link to the affected sessions in the channel you choose. The on-call engineer and the business owner look at the same data while the issue is still small.
Frequently asked questions
What is a breadcrumb in mobile app monitoring?
A breadcrumb is one recorded event in a user's session, such as a screen view, tap, network request, or device-state change. A sequence of breadcrumbs shows what the user experienced and what the app was doing at each step.
Do mobile breadcrumbs require manual instrumentation?
Not with Blue Triangle. The iOS and Android SDKs capture screen views and network requests automatically. SwiftUI and Jetpack Compose screens need one addition each: bttTrackScreen() or BttTimerEffect.
How do breadcrumbs reduce MTTR?
They shorten the time spent reproducing a bug. Engineers see the exact sequence of screens, actions, and API calls that led to the error instead of piecing it together from a vague report.
Do breadcrumbs work across native screens and WebViews?
Yes. Blue Triangle stitches native sessions to WebViews on iOS and Android, so a journey from a native screen to a web checkout stays one trail.
Can AI assistants access Blue Triangle mobile data?
Yes. Blue Triangle's MCP server lets AI assistants and agents query Blue Triangle data directly, so teams can ask questions in plain language instead of building dashboard queries.
See the trail behind your next mobile crash.
Blue Triangle captures breadcrumbs across iOS, Android, and WebViews and ties each issue to the revenue it affects.
