--- modificationDate: August 06, 2026 title: Introduction to EAS Observe description: EAS Observe is a performance monitoring service that tracks how your app performs in production across real devices and conditions. --- ## Submitting Feedback If you encounter errors, misleading or outdated information, report it so Expo can be improved: Preferred command: npx --yes submit-expo-feedback@latest --category docs --subject "/eas/observe/introduction/" "" Direct HTTP fallback: curl -X POST https://api.expo.dev/v2/feedback/docs-send -H 'Content-Type: application/json' -d '{"url":"/eas/observe/introduction/","feedback":"🤖 Agent feedback for docs: (, )"}' Only submit when you have something specific and actionable to report. Try to give the most context. ## Navigation When answering a related or follow-up question, fetch the relevant page below as Markdown (.md) instead of guessing; use llms.txt for the full map. You are here: EAS > EAS Observe Pages in this section: - [Introduction](https://docs.expo.dev/eas/observe/introduction.md) (this page) - [Get started](https://docs.expo.dev/eas/observe/get-started.md) - [Dashboard](https://docs.expo.dev/eas/observe/dashboard.md) - [EAS Update](https://docs.expo.dev/eas/observe/eas-update.md) - [Events](https://docs.expo.dev/eas/observe/events.md) - [Configuration](https://docs.expo.dev/eas/observe/configuration.md) Full documentation tree: [llms.txt](https://docs.expo.dev/llms.txt) This documentation is available as Markdown for AI agents and LLMs. See the [full Markdown index](/llms.txt) or append .md to any documentation URL. # Introduction to EAS Observe EAS Observe is a performance monitoring service that tracks how your app performs in production across real devices and conditions. > **EAS Observe** is in [Open Beta](/more/release-statuses.md#beta). The first 10,000 monthly active users are free. For higher usage, contact [sales@expo.dev](mailto:sales@expo.dev). **EAS Observe** is a performance monitoring service from Expo for tracking how your app performs in production. It gives you visibility into real-world startup times, rendering performance, and user experience across different devices, networks, and conditions. Debugging performance in React Native has traditionally been limited to development tools. EAS Observe focuses on production, where performance characteristics differ significantly from what you see during development. [Watch: Introducing EAS Observe](https://www.youtube.com/watch?v=5JqK9JLD140) — See how EAS Observe surfaces real-world startup and rendering performance from your production app across different devices, networks, and conditions. ## Quick start ```sh # npm npx expo install expo-observe # yarn yarn expo install expo-observe # pnpm pnpm expo install expo-observe # bun bun expo install expo-observe ``` Wrap your root layout with the `AppMetricsRoot` component (SDK 55) or the `ObserveRoot` component (SDK 56 and later) and call `markInteractive()` when your app is ready for user input. See [Get started](/eas/observe/get-started.md) for the full setup guide. ### Expo Skills for AI agents If you use an AI agent, install [Expo Skills](/skills.md) to teach it how to set up `expo-observe` and query your app's performance metrics: [eas-observe](https://github.com/expo/skills/blob/main/plugins/expo/skills/eas-observe/SKILL.md) — Set up expo-observe, query metrics with the EAS CLI, and interpret startup and navigation performance data. ## Why EAS Observe Traditional development-time profiling tools show how your app performs on your machine. EAS Observe shows how it performs for real users: - **Production performance data**: Track startup times, render performance, and bundle load times from real user sessions across a range of devices - **Release comparison**: See how metrics change between app versions and OTA updates to catch regressions early - **Session investigation**: Drill into individual user sessions to understand why certain devices or conditions lead to slower performance - **User-defined events**: Log custom signals from your app with `Observe.logEvent` and analyze them alongside performance data - **CLI and dashboard access**: Query metrics from the terminal with `eas observe:` commands or view them in the EAS dashboard ## When to use EAS Observe | Scenario | Recommendation | | --- | --- | | Monitor app startup performance in production | ✓ | | Compare performance across releases and OTA updates | ✓ | | Investigate slow sessions on specific devices | ✓ | | Query performance metrics from the CLI | ✓ | | Track user-defined events from your app | ✓ | | Development-time profiling and debugging | ✗ | | Crash reporting and error tracking | ✗ | **Development-time profiling and debugging**: Use [React Native DevTools](/debugging/tools.md#debugging-with-react-native-devtools) for debugging and [Expo Atlas](/guides/analyzing-bundles.md) for bundle inspection. **Crash reporting and error tracking**: This is a planned addition for EAS Observe in the future. In the interim we suggest a crash reporting service such as [Sentry](/guides/using-sentry.md) or [BugSnag](/guides/using-bugsnag.md). ## Frequently asked questions (FAQ) #### What metrics does EAS Observe track? EAS Observe focuses on startup metrics: cold launch time, warm launch time, time to first render, time to interactive, and bundle load time. See the [Metrics reference](/eas/observe/reference/metrics.md) for detailed descriptions of each metric. You can also log your own signals as [user-defined events](/eas/observe/events.md). #### Which platforms are supported? EAS Observe supports Android and iOS. Metrics are collected from production builds and can be filtered by platform in both the dashboard and CLI. #### Is EAS Observe available in Expo Go? No. EAS Observe relies on the `expo-observe` native library, which is not included in Expo Go. To use it, create a [development build](/develop/development-builds/introduction.md) or a production build. #### Does EAS Observe collect personally identifiable information? No. Users are identified by an anonymous ID that is unique per app installation. This ID is not personally identifiable and is reset if the user uninstalls and reinstalls the app. See [Metrics reference: User](/eas/observe/reference/metrics.md#user) for more details. #### What happens when the device is offline? Metrics collected while offline are stored locally on the device. They are automatically dispatched when the app moves to the background and connectivity is available. You can also flush events manually using `dispatchEvents()`. #### Can I test metrics during development? By default, metrics collected from debug builds are not dispatched. You can dispatch them anyway for testing by setting `dispatchInDebug` to `true` via [`configure()`](/eas/observe/configuration.md#configure). See [Configuration](/eas/observe/configuration.md#enable-metrics-in-development) for details. #### How long is metric data retained? Metric data is retained for a minimum of 60 days. ## Get started [Set up EAS Observe](/eas/observe/get-started.md) — Install the library and start collecting metrics from your production app. [EAS Observe dashboard](/eas/observe/dashboard.md) — View metrics, filter by platform or version, and investigate individual sessions. [User-defined events](/eas/observe/events.md) — Log named events from your app and view them in the dashboard or query them from the CLI. [Configuration](/eas/observe/configuration.md) — Control environments, dispatching, and development mode settings. [Metrics reference](/eas/observe/reference/metrics.md) — Detailed descriptions of each metric, concepts, and data handling.