React Navigation integration

Track per-screen render and interactive timings by enabling the React Navigation integration for EAS Observe.

For the complete documentation index, see llms.txt. Use this file to discover all available pages.

EAS Observe ships an opt-in integration for React Navigation that collects per-screen metrics tagged with the screen's route-name path (for example, /Tabs/Sessions). This lets you compare navigation performance by screen in the dashboard instead of looking only at app-wide aggregates.

If your app uses Expo Router, use the Expo Router integration instead. This page is for apps that use React Navigation directly.

Prerequisites

import { Observe } from 'expo-observe';

Observe.configure({
  integrations: { 'react-navigation': true },
});

import { Observe } from 'expo-observe';
import { ObserveNavigationContainer } from 'expo-observe/integrations/react-navigation';

Observe.configure({
  integrations: { 'react-navigation': true },
});

export default function App() {
  return <ObserveNavigationContainer>{/* your navigators */}</ObserveNavigationContainer>;
}

import { createStaticNavigation, useNavigationContainerRef } from '@react-navigation/native';
import { Observe } from 'expo-observe';
import { ObserveNavigationProvider } from 'expo-observe/integrations/react-navigation';

import { RootStack } from './navigation';

Observe.configure({
  integrations: { 'react-navigation': true },
});

const Navigation = createStaticNavigation(RootStack);

export default function App() {
  const navigationRef = useNavigationContainerRef();

  return (
    <ObserveNavigationProvider navigationRef={navigationRef}>
      <Navigation ref={navigationRef} />
    </ObserveNavigationProvider>
  );
}

import { useObserve } from 'expo-observe';
import { useEffect } from 'react';

export default function Home() {
  const { markInteractive } = useObserve();

  useEffect(() => {
    markInteractive();
  }, [markInteractive]);

  return (/* your screen content */);
}

Metrics

Per-screen first render (cold_ttr)

What it measures: Time from when a navigation action is dispatched (for example, navigation.navigate()) to when the destination screen first becomes focused. For the very first focus after app launch, the measurement is taken from when the JS bundle is loaded, and the event includes isAppLaunch: true.

Emitted at most once per screen instance within a session.

Event params:

Per-screen warm render (warm_ttr)

What it measures: Same as cold_ttr, but for screens that were already rendered before focus, typically because they were preloaded or the user navigated back to them. Tab-navigator siblings count as warm only once they have been mounted. With React Navigation v7's default lazy: true, unfocused tabs stay unmounted and their first focus is recorded as cold_ttr.

Event params:

Per-screen time to interactive (tti)

What it measures: Time from when a navigation action is dispatched to when markInteractive() is called on the destination screen. Only the first call per navigation is recorded, so it is safe to call markInteractive() multiple times.

Event params:

Notes and troubleshooting

• routeName is built from route names (/Tabs/Sessions), so route params never appear in the path. This keeps metrics stable across distinct param values so the dashboard buckets them together. Param values are still available on the event via routeParams.
• The integration only activates if @react-navigation/native is installed at runtime. If it is not installed, useObserve() continues to work, but no per-screen navigation metrics are emitted. Rendering <ObserveNavigationContainer> or <ObserveNavigationProvider> without @react-navigation/native throws.
• The integration must be enabled before mount via Observe.configure({ integrations: { 'react-navigation': true } }). Toggling it after the app has mounted, or after <ObserveNavigationContainer> or <ObserveNavigationProvider> has mounted, throws.
• With static configuration, pass the same ref to both <ObserveNavigationProvider> and the <Navigation> element. If the provider receives a ref that is not connected to a navigation container, no per-screen metrics are emitted.
• markInteractive() only records once the screen is focused. Calls made on an unfocused screen update internal state but do not emit a tti event until the screen is focused.
• Call useObserve() inside the screen component, not in a higher-level wrapper. If the screen's identity changes between renders, the hook logs a warning. If markInteractive() logs Calling markInteractive on unmounted screen or No metadata available for the current screen, the call ran outside a screen component or after unmount. Move the call into a useEffect inside the screen component.
• For general issues with EAS Observe, see Troubleshooting.