TraceItX
Bug reports that arrive already answered.
An in-app reporting SDK and ingest service. A user presses a bubble, draws on the screenshot, and sends. What lands on your webhook is the whole scene: UI tree, focused component, annotated screenshot, console and network state, device metadata — structured so a developer or a coding agent can act on it without asking a single follow-up question.
The problem that produced it
A bug report that says "it broke" costs a round trip. Someone has to ask which screen, which state, what the user was actually looking at. On a streaming app running across a dozen device types, that round trip is expensive, slow, and often ends with nobody able to reproduce it.
What it does
The SDK captures the context at the moment the report is made, so nothing has to be reconstructed later. Every envelope carries the serialised UI tree with the focused component marked, a screenshot the reporter can draw on, recent console and network activity, and device metadata. The ingest service validates each report and fans it out as a signed webhook to whichever receivers you configure — it is plumbing, not another dashboard to check. Payloads are retained only for the retry and dead-letter window.
Why the payload is the point
An AI coding agent can only fix what it can see. A stack trace tells it what threw; a UI tree with a focused component tells it what the person was doing when it threw. That difference is the whole product — it is why a TraceItX report can go straight into an agent and come back as a patch, rather than starting a conversation.
Where it stands
TraceItX is in active build and not yet publicly available. SDKs exist today for React on the web, native iOS, iPadOS and tvOS, and native Android on both Compose and Views, including Android TV. A React Native bridge is planned.
Runs on
- React (web)
- iOS / iPadOS
- tvOS
- Android
- Android TV