Mobile crash evidence and backend transaction evidence describe the same failure from separate starting points.
The customer needs a shared investigation path while mobile privacy and independent release cycles limit how it can be carried.
Who you’d be doing this for
“When a crash hits after checkout, we’re matching timestamps in two places and hoping we picked the same session.”
Igor Ionescu · Mobile Engineering Lead
Leads the customer’s React Native application team and coordinates incidents with backend engineers.
What is at stake
Mobile and backend developers now reconstruct failed journeys by matching timestamps across separate workflows. You must weigh a broadly reusable correlation kit against a narrower pilot that protects privacy and fits independent release cycles.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- mobile privacy vs journey correlation
- customer-specific fit vs reusable deployment kit
- open standards vs immediate operating workflow
- independent release cycles vs shared diagnosis
Why Sentry
Sentry SDKs cover React Native and Node.js, creating the foundation for a reusable cross-application diagnosis pattern.
Written with these in mind
Not your kind of problem? 20 more at Sentry, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.