# EAS Observe in production: tie startup metrics to every build and update

Crash reporters tell you when the binary died. They stay quiet when an OTA makes the home screen take three seconds longer on mid-range Android. That gap is where most "the app feels worse" tickets come from — and where release blame usually dissolves into guesswork across three native builds and two JavaScript updates.

This post is the production wiring guide for [EAS Observe](https://docs.expo.dev/eas/observe/introduction/) (`expo-observe`): install it, call `markInteractive()` honestly, read release markers next to cold/warm launch and TTI, and keep Sentry (or similar) for mature crash triage.

---

*This is an excerpt. Read the full post at [otf-kit.dev/blog/expo-observe-production](https://otf-kit.dev/blog/expo-observe-production) — full-stack kits your AI coding agent can actually ship to production. [Browse the kits →](https://otf-kit.dev)*