A tiny log console for iOS apps to display debug information directly on device without a development computer.
TinyConsole is a lightweight logging console library for iOS applications written in Swift. It allows developers to display debug information directly within their apps when a connection to a development computer isn't available, solving the problem of on-device debugging during testing.
iOS developers who need to debug applications directly on physical devices or simulators without constant computer connections, particularly useful for testing scenarios where traditional debugging methods are impractical.
Developers choose TinyConsole for its simplicity and minimal setup—it integrates easily by wrapping the main view controller and provides essential logging features without complex dependencies. Its gesture-based controls and color-coded output make debugging more intuitive during mobile development.
TinyConsole is a micro-console that can help you log and display information inside an iOS application, where having a connection to a development computer is not possible.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Wrapping the main view controller in TinyConsoleController, as shown in the README, requires minimal code changes—just modify the app delegate to set the root view controller.
Shake the device to toggle the console or use keyboard shortcuts in the simulator (⌃ctrl-⌘cmd-z), making logs accessible without interrupting development flow.
Allows printing messages with custom colors via TinyConsole.print("text", color: UIColor.green), and has dedicated methods like TinyConsole.error() for visual distinction.
Supports Carthage or manual installation without heavy dependencies, keeping the library lightweight and easy to add to projects, as emphasized in the installation section.
Focuses solely on basic logging; lacks advanced debugging tools such as log persistence, network inspection, or performance monitoring, which the README doesn't address.
Requires wrapping the root view controller, which can be cumbersome for complex app architectures or SwiftUI-based projects, and isn't easily reversible.
Logs are only displayed in-app with no default option to save or export them, limiting usefulness for post-mortem analysis or long-term debugging.