What problem does it solve? Mobile teams shipping Expo apps lack visibility into real-world startup and navigation performance, making it hard to detect slow cold launches, blocked main threads, or sluggish screens in production. ## Core Features & Use Cases - Instrumentation Setup: Add expo-observe to an Expo project by wrapping the root layout with AppMetricsRoot (SDK 55) or ObserveRoot (SDK 56+), calling markInteractive(), and optionally enabling per-route metrics via the Expo Router or React Navigation integrations. - CLI Metrics Querying: Run the five eas observe:* commands (metrics-summary, metrics, routes, events, versions) with flags for platform, time range, stats, pagination, and JSON output. - Metrics Interpretation: Apply target thresholds (cold launch < 1.5s, TTI < 3s) and use TTI frameRate params to distinguish slow-but-smooth startups from main-thread contention or hard freezes. - Use Case: After releasing a new app version, run eas observe:metrics-summary --metric tti --days 7 to compare startup TTI across versions and confirm the release did not regress launch performance. ## Quick Start Ask the assistant to add EAS Observe instrumentation to your Expo app's root layout and show how to query startup TTI metrics from the EAS CLI.