NativeScope

NativeScope is a local debugging environment for React Native applications that runs entirely offline and requires no cloud services or user accounts. It installs with a single npx command and gives you three modules for inspecting storage, network traffic, and logs, all tied together in a shared timeline so you can trace issues across layers without switching tools.

The Storage module handles AsyncStorage, MMKV, and SQLite. You can browse JSON structures visually, edit values inline, compare snapshots over time, and restore previous states if something goes wrong. That makes it useful for debugging state persistence bugs where you need to see exactly what got written and when, without adding print statements everywhere.

The Network module captures HTTP and GraphQL traffic with operation-aware timeline analysis. You see each request in context, can replay them, and track how they affected storage. If a network call triggers a state change that breaks something later, the connection is visible in the timeline rather than buried in separate logs.

The Logs module records JavaScript console output from the moment your app boots. You can inspect structured values, filter by severity, and link failures back to the requests and storage changes that happened around the same time. The unified timeline is the key piece, since most React Native debugging involves bouncing between console output, network panels, and device state. NativeScope puts all of it in one view.

Setup is minimal. You run npx nativescope, configure a single TypeScript file to declare which modules you want, and start your app. The instrumentation is dev-only by design, meaning Metro strips it out of production builds so you do not ship debugging code to users. Because everything runs locally, sensitive data like credentials and user state stays on your machine rather than flowing through a third-party server.

NativeScope is open source under Caio Barroso's GitHub. There is no paid tier or account wall. The philosophy is that debugging tools should be free and trustworthy with sensitive data, which is why it avoids the cloud entirely. If you have been stitching together Flipper plugins, Chrome DevTools, and custom logging setups, this is an attempt to consolidate that workflow into one package.