A React Native debug view for displaying and persisting log messages with performance timers and exception tracking.
React Native Device Log is a debugging tool for React Native applications that provides a visual interface for viewing log messages directly on devices. It helps developers monitor app behavior, track performance, and debug issues during development and in production environments by displaying logs in a neat list view with support for various log levels and data types.
React Native developers who need an in-app debugging tool to visualize logs, track performance, and monitor device and app state changes during development and in production.
Developers choose this over alternatives because it offers a flexible, pluggable architecture with custom storage adapters, built-in performance timers, and the ability to track exceptions with line numbers, all while being efficient and configurable for rendering and persistence limits.
A UI and service for handling/displaying dev log messages on devices
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports custom async adapters like AsyncStorage for persistence or in-memory storage, allowing developers to choose between session-based or long-term logging without vendor lock-in.
Includes log levels, performance timers, and exception tracking with line numbers, providing a full suite for in-app debugging and crash analysis in production.
Tracks device connectivity and app state changes (background, idle, active), helping developers correlate logs with environmental factors during runtime.
Allows setting maximum numbers for rendered and persisted messages, ensuring the tool remains efficient and fast even with high log volumes.
Requires initialization with storage adapters and configuration options, adding complexity compared to simple console logging, as seen in the example code.
Lacks built-in support for external logging services or advanced analytics, necessitating custom work for remote log aggregation beyond the visual interface.
Including the LogView component in production builds can clutter the UI and impact performance if not carefully managed or hidden, unlike headless logging tools.