Planned, not released
The approval that unblocks a fixshould fit in a pocket
Tore already refuses to merge anything without a person saying yes. That is the right rule and we are not softening it. What we can fix is where that person has to be standing.
Two things are coming: an app for the people running support, and proper support for the mobile apps you ship. Neither is out yet. This page is here so you can see where it is going and tell us if we have the order wrong.
Hear about it first
Crash · Northwind mobile
NullPointerException in FeedScreen
317 devices · first seen 21 minutes ago
- Classified
- InvestigatingPulled the source map for FeedScreen
- ProposedA four line null guard
A design, not a screenshot
Half one, Tore on your phone
Support does not stop because you left the building
The queue, in your pocket
Every conversation, ticket and investigation you would see at a desk, on a screen built for a thumb rather than a spreadsheet squeezed onto glass.
A push that is worth waking up for
Not every message. A breach about to happen, an escalation aimed at you, a fix waiting on your approval. The rest can wait until morning.
Approve a fix from anywhere
The whole point of the human gate is that a person looks. That person should not have to be at a laptop for a four line null guard.
Reply with your own voice
Canned responses, your help center, and the same AI draft you would get at a desk, so an answer from a train reads like an answer from the office.
Half two, the apps you ship
A crash on a phone is a support problem before it is a build problem
Crashes become investigations
A crash reported by your app becomes one investigation with its own evidence, in the same queue as everything else, rather than a separate dashboard nobody opens.
Stack traces you can read
Source maps for React Native, mapping files for Android, symbol files for iOS, so the line that failed is a line in your code and not an address.
The store release as a step
A fix for a mobile app is not merged and forgotten. It has to build, get through review, and reach devices, and the investigation should follow it that far.
What works today
If your mobile app already reports to Sentry, those issues reach Tore through the same Sentry connection as your web app, because the connection reads Sentry issues whatever produced them.
The honest limit: there is no symbolication yet, so a stack trace arrives exactly as your tracker sends it, and none of the mobile build integrations are connected. The cards for them inside Tore say so themselves rather than pretending otherwise.
The rest of Tore is not planned. It is running.
Everything else on this site works today on the web, and you can have it running against your own product this afternoon. Mobile is the part we are still building, which is why it has a page that says so instead of a badge that hides it.