qrgo

Why it's ranked here

Its case is strong because it removes several manual steps from testing QR-driven app flows. Both terminal and menu bar interfaces reach the same core workflow, while explicit device targeting supports repeatable use. The narrow URL policy and Apple-only host requirement keep it specialized rather than general-purpose.

What's good

The target chooser handles multiple running destinations and includes copy, local-open, and cancel actions. A configurable global shortcut makes repeated scans practical. The tool remembers the last scanned URL, supports direct device identifiers, removes temporary captures after processing, and reports failures instead of silently swallowing them.

Tradeoffs

The host must run macOS 12.3 or later and grant Screen Recording permission. iOS use requires Xcode and Simulator, while Android requires the SDK, ADB, and a configured device. It opens only HTTP, HTTPS, and one documented custom scheme. Homebrew is central to installation, version reporting, and menu bar updates.

How to use it well

Use it when developing mobile applications whose links arrive through QR codes, especially when repeatedly checking routing across simulators and emulators. Keep target identifiers in scripted terminal workflows, and use the menu bar shortcut for exploratory testing. It does not replace a general QR reader, physical-device lab, or broad link validator.

Observed

Primary language

Swift

Packaging

Swift Package Manager executable package with no declared package dependencies

Installation surface

Homebrew formula for the CLI and Homebrew cask for the menu bar app

Interfaces

Command-line interface and persistent macOS menu bar application

Platform support

macOS 12.3 or later

Mobile targets

Running iOS Simulators and Android devices exposed through ADB

Test structure

The package manifest declares a qrgoTests test target