EAS Observe

Overview

EAS Observe is Expo's production performance monitoring service. It tracks startup and rendering metrics from real user sessions on iOS and Android — cold/warm launch, time to first render, time to interactive, and bundle load time.

Intry uses EAS Observe alongside Sentry (crashes/errors) and product analytics — not as a replacement.

Open Beta

EAS Observe is in open beta. First 10,000 MAU free; view metrics in the EAS dashboard Observe tab or via eas observe:* CLI commands.

Role in the Intry mobile stack

Tool	Purpose
EAS Observe	Production startup/render performance; release comparison; slow-session investigation
Sentry	Crash reporting, error tracking, session replay on errors
Knock	Push delivery for buzzer alerts (not performance monitoring)
PostHog / Vexo (app)	Product analytics and funnels
expo-insights	Legacy EAS cold-start telemetry — superseded by Observe for new work

EAS Observe does not replace Sentry for crashes. Expo recommends Sentry (or BugSnag) for error tracking until Observe adds crash reporting.

Prerequisites

Requirement	Intry status
Expo account + linked EAS project	Configured (`extra.eas.projectId` in app config)
Expo SDK 55+	SDK 55 (`expo@^55`)
`expo-observe` installed	Yes — `AppMetricsRoot.wrap` in `app/_layout.tsx`
Production EAS build	Required for metrics dispatch (not Expo Go)

Integration (intry-app)

Installed and wired in tools/intry-app:

cd tools/intry-app
npx expo install expo-observe   # already in package.json
eas build --profile production  # new native build required

Root layout (app/_layout.tsx):

AppMetricsRoot.wrap(Sentry.wrap(RootLayout)) — automatic Time to First Render
ObserveReadyMarker calls markAppInteractive() after auth bootstrap + hides splash
access/[callSid].tsx also calls markAppInteractive() for push/deep-link entry

Helper: lib/markAppInteractive.ts — safe to call from any entry screen (first call wins).

expo-insights was removed in favor of EAS Observe.

Viewing metrics

Dashboard: expo.dev → project → Observe tab
CLI: eas observe:metrics-summary, eas observe:metrics, eas observe:versions
EAS Update: Compare OTA update performance between release groups

Development testing

Debug builds do not dispatch metrics by default. Enable with dispatchInDebug: true via configure() when validating integration locally.

Last verified: 2026-06-21 (commit 293c4a7)