@axonpack/expo-devtoolsReference
What needs a development build
Feature by feature, what Expo Go shows instead.
Everything not listed here works in Expo Go. The native module is loaded optionally, so a missing module dims a control instead of breaking the panel.
| Feature | Without a dev build |
|---|---|
| Main-thread frame rate | Reads dev build; the JS line still plots. |
| App memory · Device memory | Card says Needs a dev build. |
| Storage card (disk space) | Card says Needs a dev build; Android only regardless. |
| Startup, measured block | Falls back to the platform block, which may be all dashes. |
| Debug tab, Main (UI) thread | Block and crash buttons disabled with a note. |
| Native crash capture | Uncaught native exceptions are not reported. |
Platform-dependent regardless of build type
Long tasks and interactions only appear if the native side implements those entry types, which varies by platform and React Native version. When they are missing the list says so rather than showing zeros.
The Storage tab is a special case
It needs nothing from this package's native module — but the stores you register bring their own
requirements. MMKV and SecureStore carry native code of their own, so a store that needs a dev build to
exist at all also needs one to be inspectable. A store built on defineStorageAdapter alone (an
in-memory Map, say) works in Expo Go.