guide by the Buoy team

Choose React Native debugging tools by task

Updated September 16, 2026

The right tool depends on the problem, your framework version and your build. This guide compares development tools and production services, including our product, Buoy. Choose Buoy for in-app inspection and supported test controls; keep source debuggers and monitoring for the tasks they handle.

React Native DevTools: source debugging

Start here for JavaScript breakpoints and React inspection. Current documentation also covers Network and Performance panels from React Native 0.83. Read the official DevTools guide for the capabilities of your version and the separate native-debugging workflow.

Buoy: in-app inspection and test controls

Buoy puts supported network, storage and state inspectors inside your app. Developers can add custom controls for authorized QA and support staff. A Free account includes Desktop at Free limits. Pro adds MCP, paid controls and supported React Native release use. Flutter has different, debug-only coverage.

Install the tools your app needs and configure their adapters. Capture is limited by supported data sources, startup order and retention. For release use, restrict access, authorize backend actions and configure release sync explicitly. Follow the quick start and plan comparison.

Reactotron: desktop inspection

Reactotron provides a free, open-source desktop workflow with app-state, network and logging integrations. Review its overview and MCP guide if agent access matters. Its maintainer guidance favors development-only setup. Our Buoy comparison explains the integration and release-use differences.

Rozenite: DevTools panels and agent tools

Callstack’s Rozenite adds panels for network activity, storage, Redux, TanStack Query and navigation. It supports custom plugins and agent tools, so it is a direct alternative for developers who want library inspectors in their DevTools workflow.

Choose Buoy when your tester needs to inspect the app from the device’s floating menu. Its Time Machine can restore registered client-state sources together, and Ask Buoy gives Pro users an in-app assistant for configured tools. Ask Buoy is in beta and needs a model endpoint. Compare the exact actions each integration exposes.

Radon: debugging inside your editor

Radon integrates app previews, element inspection, breakpoints and a network inspector into VS Code and Cursor. See Software Mansion's feature overview. Its release notes also document MCP tooling. Evaluate the supported editor, platform, version and license for your project instead of assuming that agent access is unique to Buoy.

Expo tools: the framework's development workflow

Expo provides a developer menu, DevTools access and development-tool integrations. Check the Expo debugging guide for your SDK and build type. Expo Go and a custom development build do not have identical native dependencies or capabilities.

Sentry: errors from deployed apps

The official Sentry React Native SDK captures JavaScript errors and native crashes and supports performance instrumentation. Use this category of tool when you need reports from deployed apps. Configure collection and verify a test error; an in-app inspector alone does not provide fleet-wide incident reporting.

Network proxies: inspect traffic beyond app hooks

Charles, Proxyman, HTTP Toolkit and Fiddler Everywhere can inspect and modify intercepted traffic. They are useful when a native client bypasses Buoy’s global fetch or XMLHttpRequest hooks. HTTPS capture depends on the proxy setup and the app’s certificate trust behavior.

Buoy gives you supported request details on the device, next to your state and storage inspectors, without configuring an HTTPS interception certificate. Its development-only overrides let you exercise error responses interactively. For mocks maintained in code, also consider Mock Service Worker. Check capture and override limits against the clients your app actually uses.

State and render packages: focus on one problem

Redux DevTools covers state changes and action replay. Jotai DevTools documents a web UI for atoms, so check native integration separately. TanStack’s React Native guide lists Query inspector integrations. For render diagnostics, why-did-you-render supports React Native. Check React and runtime compatibility for each package.

Choose Buoy when you need several of these views in the app. Its installed tools share a menu, and supported tools are accessible through Desktop or Pro MCP after connection setup. Store registration and provider requirements still apply. A focused package may be enough if you only need one library’s inspector.

Monitoring SaaS: investigate deployed sessions

Alongside Sentry, evaluate BugSnag and Firebase Crashlytics through React Native Firebase for error or crash reporting. LogRocket documents mobile replay and logs. Luciq / Instabug includes in-app bug reporting, replay and performance monitoring.

Datadog RUM covers user journeys and mobile performance. New Relic documents mobile errors, network instrumentation and distributed tracing. Embrace maps mobile telemetry to OpenTelemetry signals and supports custom exporters. Compare collection, retention and pricing for your actual traffic.

Buoy helps with the reproduction: inspect captured requests, edit registered state and repeat the test. It does not replace incident reporting across deployed apps. For Sentry users, Buoy’s Sentry inspector shows captured JavaScript envelopes and diagnostic estimates on the device. Spotlight is another local debugging option, with Sentry events and MCP access.

Legacy tools: check the migration path

Flipper’s repository was archived on September 26, 2025. Its README identifies v0.239.0 as the last release supporting React Native. Expo also documents that React Native Debugger relies on deprecated remote JavaScript debugging and is incompatible with Hermes. Use our Flipper migration comparison to map existing inspectors to current tools.

Make a small evaluation plan

Your taskOptions to evaluateVerify in your app
Step through JavaScriptReact Native DevTools; RadonRuntime and framework compatibility
Inspect app dataBuoy; Reactotron; Rozenite; Expo pluginsActual transports, adapters and retention
Give QA in-app controlsBuoy and app-specific toolsSetup, authorization and plan limits
Let an agent inspect a running appBuoy; Reactotron; Rozenite; Radon; SpotlightAvailable commands and shared data
Collect deployed-app errorsSentry; BugSnag; Crashlytics; mobile monitoring servicesNative setup, collection settings and a test event
Repeat a client-state setupBuoy Time Machine; library-specific state toolsRegistered sources, restore results and unchanged backend state

Reproduce one bug, record what each tool captures, and check setup effort and overhead on your target devices. Keep the tools that help with tasks your team actually performs. A feature checklist cannot establish compatibility with your app.

Sources and review scope

We reviewed the linked maintainer documentation and product pages on September 15, 2026. These are workflow recommendations by the Buoy team, not benchmark results. The comparison hub lists the alternatives and explains where Buoy helps alongside them.

What should I replace Flipper with?

List the plugins and actions you use first. Choose source debugging, app inspection and native tooling separately; a single product may not cover all of them.

Can I inspect production behavior?

Use monitoring for reports from deployed apps. Supported Buoy React Native tools can provide authorized in-app inspection with Pro; this requires release setup and does not recover uncaptured past sessions.

Evaluate Buoy on one debugging task

Start with a Free account. Follow the quick start for package requirements, account setup and tool integration.

Quick startnpm i @buoy-gg/core

sources

Capability claims on this page come from each vendor's own documentation, read on the date shown. We did not install and run every tool listed.