Silent failures
Your crash reporter says the app is fine. Users are still leaving.
Rage click detection, dead taps and crash-free rate tracking in one SDK. If you are trying to work out why users drop off an app when nothing crashed, the answer is usually breakage that never threw an exception — and your mobile app error monitoring never saw it.
Free under 1M events a month. React Native, Flutter and web.
Why users drop off an app when nothing crashed
A crash is loud. Someone gets a stack trace, a ticket gets filed, it gets fixed. The far more common failure is silent — and none of it produces an exception, so none of it reaches Crashlytics or Sentry. Your crash-free rate stays at 99.8% and looks healthy, and the user closed the app and did not come back.
Nohmo reads the session journey instead of waiting for a stack trace. Every detector asks a behavioural question rather than a technical one: an intent was expressed, and nothing answered it.
What gets detected
Dead tap
A tap on something tappable, followed by silence. No navigation, no event, no request — the app simply did not answer.
Rage click, no error
Three fast taps on the same control with no error behind them. The user is telling you it is broken; nothing in your stack agrees.
Form submitted into the void
A form submitted, and the app neither navigated nor confirmed. The user cannot tell whether it worked, so they try again or leave.
Empty successful response
A request that returned 200 with an empty body. Technically a success, visibly a blank screen.
Ranked by the sessions abandoned right after
A list of broken buttons is a chore. Nohmo groups each failure by the control that broke and sorts by how often the user gave up immediately afterwards, so the top of the list is the thing costing you users today — not the thing that happens most often.
Silent signals
Every detection in the period
Sessions affected
How many people hit it
Abandoned after
How many gave up right there
Distinct issues
Grouped by control, not by event
Crash-free rate tracking and mobile app error monitoring, in the same SDK
Silent failures are the half nobody measures, not a replacement for the half everybody does. Nohmo captures native iOS and Android crashes, JavaScript and Dart errors, and failed network requests — with crash-free rate per release and a flag when a new build is crashing more than the one it replaced.
Because it is one SDK with one identity model, a crash and the funnel step it happened on are the same session. That is the question three separate tools cannot answer between them: a user crashed — where were they in signup when it happened?
Rage click detection with no per-button code
On React Native a Babel plugin rewrites every onPress at build time. On Flutter a single wrapper widget walks the render tree to the tap point. Either way you add one line, not one line per button — and every tap arrives with the component name, the visible label and the path to it.