The open-source Firebase Crashlytics alternative, built for mobile

A Crashlytics crash report gives you a stack trace and whatever breadcrumbs you instrumented ahead of time. Taps, navigations, network calls and lifecycle transitions each need their own instrumentation, and this needs to keep up with code changes resulting in an error prone process with missing context as the app evolves.

Measure auto-captures gestures, navigation, lifecycle events, network calls and traces, then replays them as a Session Replay attached to every crash, ANR and error.

The debugging process changes from guesses about what happened to facts you can observe. Instead of reading a stack trace, forming a hypothesis, shipping breadcrumbs and waiting a release cycle to test it, you just open the issue and watch what happened. Even better, just point your agent at the issue and it can use our MCP Server to fetch deep context across several occurrences to help you find the root cause. The hardest to reproduce issues: a crash that only happens on a certain device in a specific navigation path, an error that only occurs when a background request times out before completion, a failure that depends on state built up over several screens, become easier than ever to fix.

Crashlytics is part of Firebase, where mobile is one product line among many and roadmap decisions compete with everything else on the platform.

Measure is built only for mobile. Crashes & ANRs, App Health, Performance Traces, Network Performance, Bug Reports and User Journeys are all designed around the failure modes mobile apps experience in production: memory pressure, main-thread blocking, errors during background and foreground transitions, and unstable network conditions.

Mobile is not a part of our product. It is the whole product.

Crashlytics publishes its SDKs on GitHub, but the backend and dashboard are proprietary and run only on Google's infrastructure.

Measure is open source end to end under an Apache 2.0 license. You can read the code, run it, self-host it, and audit how data is collected and stored. If you have ideas on how to make it better, you can open an issue or send a pull request.

Open source software is better for transparency because you can see the code handling your data. It's better for security since more eyes on the code lead to more discovered vulnerabilities. It is better for flexibility, since you can raise issues and PRs to improve the platform or host it yourself if you have the need. Being open source also makes Measure easier to use with coding agents - just point your agent at the code or docs and it can figure out everything it needs to make full use of everything the platform offers without poking around a black box.

Measure supports Android, iOS, iPadOS, Flutter, React Native and Kotlin Multiplatform.

Our SDKs are designed to be thoughtful, flexible, lightweight and performant across all platforms. Crashes, ANRs, performance traces, network monitoring and session context are tracked, symbolicated and collected with platform-specific best practices in mind so that observability doesn't impact the performance of the app itself.

Data across all your Android, iOS and cross-platform apps, along with their dev, staging and production variants feeds into a single unified dashboard so you can ship and monitor your apps with confidence.

Crashlytics crash reporting is free but data export and advanced analysis depend on separate products with independent pricing. Products like BigQuery export for custom analysis, Cloud Functions for custom alerting, Google analytics for user interaction events lead to platform lock-in and hard to predict costs as apps scale.

Measure has a single price based on how much data you send. No per-seat charges, no arbitrary feature bundles. Raw data export is available in enterprise plans to a destination you choose without restriction to a particular cloud or vendor. With Adaptive Capture you can adjust data collection rates without shipping an app update, which makes it easy to scale telemetry when your app needs to while keeping costs under control.

Measure is useful for any mobile app but it fits best for apps with growing users, complexity and scale. If production issues are getting harder to debug due to missing information about the states that led to them, or if users are complaining about performance and network issues and your current setup lacks deep telemetry and context to fix them, Measure will fit like a glove.

Measure can also be a good choice if data ownership, auditability of the platform and avoiding platform lock-in to a single ecosystem matters to you for security or compliance reasons.

If simple crash reporting is all you need, and your team is already comfortable inside the Google ecosystem, Crashlytics is a decent option. Measure is designed for growing mobile teams that need production observability at scale. With deep telemetry, Measure makes fixing issues with agents and shipping amazing mobile experiences easier and faster.

Switching to Measure does not have to be a rip-and-replace. You can install the Measure SDK and run it alongside Crashlytics while you evaluate. A generous free tier lets you integrate your app, send telemetry data, use session replays, performance traces and MCP server integration to debug issues and see how Measure helps improve your app.

Many teams use both Crashlytics and Measure together until they make the switch. Setup and per-platform guides are in the docs.