When to Use

• Use when this upstream workflow matches the user's stated goal.
• Use when the task requires the procedures documented in this skill.

EAS Observe

EAS service - costs apply. EAS Observe is an Expo Application Services product. The free EAS plan allows up to 10,000 monthly active users, with a limited set of features; higher usage requires a paid subscription. For details, see https://expo.dev/pricing#plan-features.

EAS Observe tracks startup, navigation, and custom-event performance from production Expo apps. It needs a development or production build — the native library is not in Expo Go.

Source of truth: https://docs.expo.dev/eas/observe/ — 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.

Authorization and privacy

Confirm the existing EAS account/project, telemetry data policy and current plan before enabling collection, sending events or starting paid builds. Adding instrumentation can transmit routes, identifiers, error messages/stacks and request hosts. Do not collect secrets or unnecessary personal data; use synthetic test data, review route filtering before enabling integrations, and verify behavior on the installed SDK. Do not redirect telemetry to a custom endpoint without authorization. Preparing an integration does not authorize EAS project creation, dependency-wide repair, builds or feedback submission. Feedback commands download and execute a package and send data externally; use only when explicitly requested, with redacted content.

Which reference to read

The four reference files in ./references/ cover what people typically need this skill for: