Eas Observe

EAS service - costs apply. EAS Observe is a paid Expo Application Services product with free-tier limits. Ingesting and querying production metrics counts against your plan’s event/usage allowance. Review https://expo.dev/pricing (opens in a new tab) before enabling it in production.

EAS Observe tracks startup, navigation, and custom-event performance from production Expo apps.

Source of truth: https://docs.expo.dev/eas/observe/ (opens in a new tab) — always consult the canonical docs when API details matter, especially get-started, configuration, integrations, and the metrics reference. EAS Observe is evolving; this skill’s references are written to stay accurate but may lag the docs.

Which reference to read

The three reference files in ./references/ cover the three things people typically need this skill for:

• Adding EAS Observe to a project → ./references/setup.md (opens in a new tab). Install, wrap the root layout (AppMetricsRoot on SDK 55, ObserveRoot on SDK 56+), call markInteractive() (global on SDK 55, via the useObserve() hook on SDK 56+), optional per-route navigation metrics through the Expo Router / React Navigation integrations, and user-defined events via Observe.logEvent (SDK 56+).
• Querying metrics from the terminal → ./references/queries.md (opens in a new tab). The five eas observe:* commands — metrics-summary, metrics, routes, events, versions — with flags, table layouts, JSON shapes, and common workflows.
• Reading a dashboard or CLI output → ./references/metrics.md (opens in a new tab). Target thresholds per metric, what the TTI frameRate.* params mean, and diagnostic patterns for telling slow-but-smooth startup apart from main-thread contention or hard blocks.

Quick links to the docs

• Get started: https://docs.expo.dev/eas/observe/get-started/ (opens in a new tab)
• Dashboard guide: https://docs.expo.dev/eas/observe/dashboard/ (opens in a new tab)
• Metrics reference: https://docs.expo.dev/eas/observe/reference/metrics/ (opens in a new tab)
• Expo Router integration: https://docs.expo.dev/eas/observe/integrations/expo-router/ (opens in a new tab)
• React Navigation integration: https://docs.expo.dev/eas/observe/integrations/react-navigation/ (opens in a new tab)
• User-defined events: https://docs.expo.dev/eas/observe/events/ (opens in a new tab)
• Configuration: https://docs.expo.dev/eas/observe/configuration/ (opens in a new tab)

Submitting Feedback

If you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:

npx --yes submit-expo-feedback@latest --category skills --subject "eas-observe" "<actionable feedback>"

Only submit when you have something specific and actionable to report. Include as much relevant context as possible. If an AI agent repeatedly failed or the user had to take over an Expo task, load the expo-skill-feedback skill and follow its eval-candidate flow instead of reusing the command above.