nikeight

Most app issues aren't hard to fix. The hard part is figuring out what happened. We kept running into this ourselves. You open Crashlytics, then analytics, then a few more tools. You jump between tabs trying to reproduce the issue yourself. Hours spent just reconstructing context. That's the real problem. Not fixing. Understanding. @measure_sh gives you a session timeline. User actions, network calls, logs, lifecycle events, device signals, all in one place. Most of it is collected automatically, so you don't run into "we forgot to log this". That already makes correlation much easier. This week we added MCP support. Now you don't have to break your flow to analyze everything. Instead of reading through logs and traces step by step, you can just ask "What caused this issue?" in your favorite coding agent like Claude Code or Codex. And get a clear breakdown of what happened, where it broke, why it broke, and what needs to change. No tab switching. No breaking your flow. More shipping. Measure is now generally available, just sign up and get to the root cause → measure.sh