---
id: gh-expo-observe
name: "expo-observe"
url: https://skills.yangsir.net/skill/gh-expo-observe
author: expo
domain: ai-system-observability-sre
tags: ["observability", "performance-monitoring", "mobile-performance", "expo", "metrics"]
install_count: 6200
rating: 4.40 (120 reviews)
github: https://github.com/expo/skills/tree/main/plugins/expo/skills/expo-observe
---

# expo-observe

> 此技能用于跟踪 Expo 应用的启动、导航和自定义事件性能。它提供 CLI 工具来查询和解读冷启动、热启动、TTR、TTI 等关键指标，帮助开发者识别并解决性能瓶颈，优化用户体验，确保应用高效稳定运行。

**Stats**: 6,200 installs · 4.4/5 (120 reviews)

## Before / After 对比

### 移动应用性能问题诊断效率

**Before**:

在没有这个技能之前，开发者需要手动猜测或依赖用户反馈来定位移动应用的性能问题，这通常涉及耗时的日志分析和反复测试，导致问题诊断周期长，用户体验受损。

**After**:

该 Skill 能够提供详细的启动、导航和自定义事件性能数据，开发者可以快速识别性能瓶颈，精准定位问题根源，大幅缩短诊断时间，提升应用质量和用户满意度。

| Metric | Before | After | Change |
|---|---|---|---|
| 性能问题诊断时间 | 60分钟 | 10分钟 | -83% |

## Readme

# EAS Observe

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

> **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.

## 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`](./references/setup.md). 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+), and optional per-route navigation metrics through the Expo Router / React Navigation integrations.
- **Querying metrics from the terminal** → [`./references/queries.md`](./references/queries.md). 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`](./references/metrics.md). 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/
- Dashboard guide: https://docs.expo.dev/eas/observe/dashboard/
- Metrics reference: https://docs.expo.dev/eas/observe/reference/metrics/
- Expo Router integration: https://docs.expo.dev/eas/observe/integrations/expo-router/
- React Navigation integration: https://docs.expo.dev/eas/observe/integrations/react-navigation/
- Configuration: https://docs.expo.dev/eas/observe/configuration/


---
*Source: https://skills.yangsir.net/skill/gh-expo-observe*
*Markdown mirror: https://skills.yangsir.net/api/skill/gh-expo-observe/markdown*